How can you assure yourself that important files retain their data intact? Here’s a simple strategy for doing that, which works better on a file system that doesn’t check integrity.
cintch
APFS checks file system metadata, not file data. Consistency Scan has gone missing, verifying checksums doesn’t appear to verify data, and Verify Integrity seems to do something altogether different.
For Finder aliases, writing entries in the log, checking file integrity, comparing extended attributes, normalising text to Unicode Forms, and running the same checks as SilentKnight.
What are the performance differences between SHA-256 and 512? What throughput can you expect when checking hashes? And how to correct errors detected?
From its outset, APFS hasn’t tested the integrity of file data stored on it. Would this be a good idea, or should macOS switch to the ZFS file system instead?
APFS has no feature to check file data integrity. Dintch and Fintch are two apps that tag files with SHA-256 hashes to address this. New versions.
How to do this using macOS and free tools. Introduces a new version of Dintch which lets you control its speed, particularly on Apple silicon.
Storage has to be reliable, efficient and resilient. However, efficiency and resilience oppose one another. What’s the best solution? New file formats, CRC in the file system, or what?
Updates replace an expiring developer ID installer certificate. All are Universal binaries, fully signed and notarized.
For many users, it’s essential to be able to check the integrity of the data which are in a backup. This feature has changed when backing up to APFS.
The Eclectic Light Company 