This can now be incorporated into your own scripts, to check the integrity of important files automatically.
Can you use error-correcting code to repair very large files, for example of around 20 GB or more?
Simply having ECC enabled doesn’t mean that damaged files can be recovered. It appears promising, but needs careful real-world evaluation.
We assume what we know to be impossible, and pretend that just making ‘safe’ copies of important documents will preserve them for the future.
Do you want ECC for your important documents? It’s available now, free, without the complications of ZFS or cost of RAID 6.
A nimbler version of Dintch is designed to drag and drop files and smaller folders to tag then and check their integrity.
More about checking the integrity of files on macOS, with a new version of a free utility, news of the next apps, and error-correcting code perhaps?
To check the integrity of important documents, we’re going to calculate their SHA256 digests. But where should those be stored if HFS+ and APFS don’t have a suitable attribute?
If macOS can’t do it, how should we check the integrity of important files? Use a checksum, or a hash function? And which?
We take for granted that our files remain uncorrupted, but know that isn’t always true. How can we fix or even detect such changes?