Re:A ZFS developer’s analysis of Apple’s new APFS file system
by liw on Sunday June 26, 2016 @03:00PM
(#11982107)
It tells you that your file is corrupted. You can then restore from backups, re-download, or take some other corrective action, such as delete the file, reboot the machine, re-install the operating system, or play Quake 2 to test your RAM and graphics.
Never underestimate the value of a reason to play Quake 2.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by Zardoz84 on Sunday June 26, 2016 @06:32PM
(#11983111)
I remember when I played DooM to test and benchmark a computer...
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by radiowave on Sunday June 26, 2016 @03:05PM
(#11982128)
The average user might have no redundancy, but they still ought to have a backup. Checksum failure tells them they need to restore.
At the very least, a checksum failure might tell them (or the tech they're consulting) that they have a data problem, rather than, say, an application compatibility problem.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by XorNot on Sunday June 26, 2016 @04:12PM
(#11982456)
"Why is my machine crashing?" "Well, somelib.so is reporting checksum failures" is a much better experience then "weird, this machine used to be great but now it crashes all the time"
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by astrange on Sunday June 26, 2016 @09:53PM
(#11983776)
Most all executable files are already codesigned, which is a better version of checksums, so it'd only help user data files.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by kartickv on Sunday June 26, 2016 @09:45PM
(#11983755)
somelib.so what? And what's a "checksum"? Error messages need to be comprehensible to the average user.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by brokenmachine on Wednesday June 29, 2016 @02:47AM
(#11999926)
"Error: Buy a new Mac."
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by kartickv on Sunday July 03, 2016 @11:40AM
(#12026352)
Assuming your intent is not to troll: "The file xyz.txt is corrupt. Click here to restore from a Time Machine backup."
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by mindajar on Sunday June 26, 2016 @04:25PM
(#11982510)
Today you can verify backups on OS X with "tmutil verifychecksums", at least on 10.11. The UI to this could be improved, but user data checksums don't necessarily need to be a filesystem feature. On a single-disk device, the FS doesn't have enough information to do anything useful about corrupt files anyway.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by vardump on Sunday June 26, 2016 @05:38PM
(#11982866)
> On a single-disk device, the FS doesn't have enough information to do anything useful about corrupt files anyway.
Some filesystems can be configured to keep two or more copies of certain filesystem/directory/etc. contents. Two copies is enough information to do something useful.
Re:A ZFS developer’s analysis of Apple’s new APFS file system
by comex on Sunday June 26, 2016 @03:34PM
(#11982275)
Well, Apple is moving in the direction of syncing everything with iCloud - iCloud Drive has been around for a while, and Sierra adds the ability to sync the desktop and Documents folder; of course on top of long-existing things like photo sync. If the file was previously uploaded to iCloud, there is redundancy, and you definitely don't want to overwrite it with the corrupted version.
How big an issue this is in practice I don't know.
I mean, it'll tell you that your only copy of a file got corrupted, but it'll still be corrupted...