| |
| ▲ | fluoridation 3 days ago | parent | next [-] | | So don't upgrade it. Export it to an agnostic format and re-import it in the new version. Since it's failing to upgrade, it must be a metadata issue, not a data issue, so removing the Blender-specific bits will fix it. What a silly hypothetical. There's a myriad freak occurrences that could make you have to redo work that you don't worry about. Now, I'm not saying single-bit errors don't happen. They just typically don't result in the sort of cascading failure you're describing. | | |
| ▲ | cma 3 days ago | parent [-] | | Doing a lossy export/reimport process probably isn't going to be viable on something like a big movie scene blender file with lots of constraints, scripted modifiers and stuff that doesn't automatically come through with an export to USD. My point is that there are scenarios where corruption in the past puts you in a bind and can cause a lot of loss of work or expensive diagnostic and recovery process long after it first occurred, blender was just one example but it can be much worse with proprietary software binary formats where you don't have any chance of jumping into the debugger to figure out what's going wrong with an upgrade or export. And maybe the subscription version of it won't even let you go back to the old version. > There's a myriad freak occurrences that could make you have to redo work that you don't worry about. Yes other sources of corruption are more likely from things like software errors. It's not that you wouldn't worry about them if you had unlimited budget and could have people audit the code etc., but you do have a budget and ECC is much cheaper relative to that. That doesn't mean it always makes sense for everyone to pay more for ECC. But I can see why people working on gigantic CAD files for nuclear reactor design, etc. tend to have workstations with ECC. | | |
| ▲ | fluoridation 3 days ago | parent [-] | | >a big movie scene blender file with lots of constraints, scripted modifiers and stuff Not really what I would call an "asset", but fine. >It's not that you wouldn't worry about them if you had unlimited budget and could have people audit the code etc. Hell, I was thinking something way simpler, like your cat climbing on the case and throwing up through the top vents, or you tripping and dropping your ass on your desk and sending everything flying. >But I can see why people working on gigantic CAD files for nuclear reactor design, etc. tend to have workstations with ECC. Yeah, because those people aren't buying their own machines. If the credit card is yours and you're not doing something super critical, you're probably better served by a faster processor than by worrying against freak accidents. |
|
| |
| ▲ | coldtea 3 days ago | parent | prev [-] | | >Let's say you corrupted one bit in a blender asset 200 revisions ago and it was unnoticeable and still upgraded through five blender upgrades, but now on the sixth upgrade it fails with a corruption error and doesn't upgrade. And let's say you have archived copies of it with checksums like I suggested, going back to all revisions ago. What's the issue again now, that ECC would have solved? Not to mention that ECC wouldn't help at all with corruption at the disk level anyway. | | |
| ▲ | fluoridation 3 days ago | parent [-] | | >What's the issue again now, that ECC would have solved? If the bit flip happened in RAM, the checksum would be of the corrupted data. ECC corrects single bit errors of data on RAM. >Not to mention that ECC wouldn't help at all with corruption at the disk level anyway. Yes, using ECC without ZFS, btrfs, ReFS, or checksummed file formats is pretty pointless (unless your application never touches storage). |
|
|
