On Thu, Oct 15, 2015 at 10:40 AM, Rich Freeman <[email protected]> wrote: > On Wed, Oct 14, 2015 at 9:47 PM, Chris Murphy <[email protected]> wrote: >> >> For that matter, now that GlusterFS has checksums and snapshots... > > Interesting - I haven't kept up with that. Does it actually do > end-to-end checksums? That is, compute the checksum at the time of > storage, store the checksum in the metadata somehow, and ensure the > checksum matches when data is retrieved?
http://www.gluster.org/community/documentation/index.php/Features/BitRot It could be argued that since checksums are computed after writing, that SDC has already happened by the time the checksum is computed and written (I also don't know if the metadata itself is checksummed so the checksum could be wrong maybe and we don't know that?). But yes it's stored checksum. It can be enabled to check on read/open but by default it only does verification with scrubs. And the checksums are per file, and are SHA256 based. So it's different than Btrfs, and it's passive. But it's there. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
