On 27 Oct 2012 23:02 +0100, from h...@carfax.org.uk (Hugo Mills): >> I came across the tidbit that ZFS has a contract guarantee that the >> data read back will either be correct (the checksum computed over the >> data read from the disk matches the checksum stored on disk), or you >> get an I/O error. Obviously, this greatly reduces the probability that >> the data is invalid. (Particularly when taken in combination with the >> disk firmware's own ECC and checksumming.) >> >> With the default options, does btrfs make any similar guarantees? If >> not, then are there any options to force it to make such guarantees? > > It does indeed do the same thing: if the checksum doesn't match the > block, then the alternative block is read (if one exists, e.g. RAID-1, > RAID-10). If that does not exist, or also has a checksum failure, then > EIO is returned.
Great! This should perhaps be mentioned more clearly in the Wiki. Also, thanks for the prompt reply. -- Michael Kjörling • http://michael.kjorling.se • mich...@kjorling.se “People who think they know everything really annoy those of us who know we don’t.” (Bjarne Stroustrup) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
