4 ms·
Unless he is talking about scrubbing and self-healing? In which case, the same thing still applies -- all releases do this as far as I know. See: https://pthre
by stewartbutler 11y ago
Unless he is talking about scrubbing and self-healing? In which case, the same thing still applies -- all releases do this as far as I know.
See: https://pthree.org/2012/12/11/zfs-administration-part-vi-scrub-and-resilver/ https://pthree.org/2012/12/11/zfs-administration-part-vi-scr...
- throwaway7767 11y agoWell, scrubbing and self-healing are really just the user-facing operations enabled by the erasure coding, so it's really the same thing.
- usefulcat 11y agoAFAIK zfs doesn't use erasure coding. It has a checksum for each block. Together with redundant storage of blocks, this allows it to determine which block is corrupt when two copies of the same block have different contents.
- jamesblonde 11y agoRedundant storage of the meta data - not the actual blocks. But at least you know they're corrupted if the become corrupted ;)
- usefulcat 11y agoNope, all blocks, unless wikipedia is wrong or I am completely misunderstanding the following: "When a block is accessed, regardless of whether it is data or meta-data, its checksum is calculated and compared with the stored checksum value of what it "should" be. If the checksums match, the data are passed up the programming stack to the process that asked for it; if the values do not match, then ZFS can heal the data if the storage pool provides data redundancy (such as with internal mirroring), assuming that the copy of data is undamaged and with matching checksums." https://en.wikipedia.org/wiki/ZFS https://en.wikipedia.org/wiki/ZFS