Checksums
conceptYou trust a disk the way you trust a filing cabinet: what you put in is what you'll get back. Mostly, that's true. But disks age and glitch, and once in a long while one hands back subtly wrong data while reporting that everything is fine—no error, no warning, just wrong bytes. Keeping duplicate copies doesn't escape this: with two copies that disagree and no referee, which one is right?
ZFS's referee is the checksum: a tiny fingerprint computed from every piece of data as it's written. Every time anything is read back, ZFS re-computes the fingerprint and compares—so wrong data gets caught the moment anything touches it. Hold two powers apart, because everything downstream depends on the split: noticing damage is guaranteed, everywhere, always. Fixing damage requires a spare copy to fix it from. Fingerprints alone can only tell you what you lost—they can't give it back.