On 2017-08-13 10:16, Goffredo Baroncelli wrote:
Hi all,
in the BTRFS wiki, in the status page, in the "line" RAID5/6 it is reported
that the parity is not checksummed. This was reported several time in the ML and also on
other site (e.g. phoronix) as a BTRFS defect.
However I was unable to understand it, and I am supposing that this is a false
mith.
So my question is: the fact that in the BTRFS5/6 the parity is not checksummed
could be considered a defect ?
My goal is to verify if there is a rationale to require the parity checksummed,
and if no I would like to remove this from the wiki.
While there isn't for normal operation (as Chris did a good job of
explaining), there is a benefit for scrubbing the filesystem.
Without checksummed parity, you have to verify checksums on all the
data, and then either recompute and compare the parity, or recompute and
compare the data from parity to be able to verify that everything is
correct.
With checksummed parity you just verify checksums on everything.
So, overall, I wouldn't consider it a defect, but having it could
improve performance for a very specific use case.
--
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
