Ummm… there's a difference between data integrity and data corruption. Integrity is enforced programmatically by something like a DBMS. This sets up basic rules that ensure the programmer, program or algorithm adhere to a level of sanity and bounds.
Corruption is where cosmic rays, bit rot, malware or some other item writes to the block level. ZFS protects systems from a lot of this by the way it's constructed to keep metadata, checksums, and duplicates of critical data. If the filesystem is given bad data it will faithfully lay it down on disk. If that faulty data gets corrupt, ZFS will come in and save the day. Regards, Mike On Nov 16, 2010, at 11:28, Edward Ned Harvey <sh...@nedharvey.com> wrote: >> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss- >> boun...@opensolaris.org] On Behalf Of Toby Thain >> >> The corruption will at least be detected by a scrub, even in cases where > it >> cannot be repaired. > > Not necessarily. Let's suppose you have some bad memory, and no ECC. Your > application does 1 + 1 = 3. Then your application writes the answer to a > file. Without ECC, the corruption happened in memory and went undetected. > Then the corruption was written to file, with a correct checksum. So in > fact it's not filesystem corruption, and ZFS will correctly mark the > filesystem as clean and free of checksum errors. > > In conclusion: > > Use ECC if you care about your data. > Do backups if you care about your data. > > Don't be a cheapskate, or else, don't complain when you get bitten by lack > of adequate data protection. > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
