| ▲ | coldtea 3 days ago | |
>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). | ||