42 ms·
Note that ZFS isn't magic. Even with ZFS's checksums on read, you should still be doing regular scrubs, just like you should be with LVM or btrfs. And once y
by bryanlarsen 11y ago
Note that ZFS isn't magic. Even with ZFS's checksums on read, you should still be doing regular scrubs, just like you should be with LVM or btrfs. And once you have regular scrubs, checksums on read don't really add much.
- heavenlyhash 11y agoAgreed, turning on more safety features will always make you... safer :) But it's worth noting that I've debugged corruptions in prod systems where: - corrupted data was read from disk -- a bit flip, with no error code at the time -- by an application - the application operated on it - and the application then wrote the result -- still carrying the bit flip -- back to a new file on disk. Ouch. The bitflip is now baked in and even looks like a legit block as far as the disk is concerned. The disk failed not long after, of course -- SMART status caught up, etc. But that was days later. Checksums on read address this. I never want to run a system without them again.
- bryanlarsen 11y agoI don't understand. If the bit was flipped before or during read the scrub would catch it. If it was flipped by the application then no file system can help. How does read checksums help you?
- mrighele 11y agoThere is still the chance that data get corrupted between the time the scrub is performed and the time you read the data, so I don't consider scrubs sufficient. In any case you are right, they should be performed even with ZFS, expecially to test data that is rarely or never read back.
- bryanlarsen 11y agoSure, there can be one error between scrub and read. But assuming RAID, you need errors on two disks. That can happen in a week or however often you scrub, but that's going to be pretty low probability.
- heavenlyhash 11y agoYou assume that your RAID implementation is going to actually read all of its parity bits from each of the disks, and check them for agreement, before returning a value to you. You may want to validate that assumption. :) (Prepare for an unpleasant surprise.)