From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: kreijack@inwind.it, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC] Checksum of the parity
Date: Mon, 14 Aug 2017 09:23:54 -0400 [thread overview]
Message-ID: <2aac70ec-cef4-3b5d-b4ef-7b6d94c32489@gmail.com> (raw)
In-Reply-To: <5d703b4c-e8ac-21dc-e327-ff1d8e232ee9@inwind.it>
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.
prev parent reply other threads:[~2017-08-14 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 14:16 [RFC] Checksum of the parity Goffredo Baroncelli
2017-08-13 18:45 ` Chris Murphy
2017-08-13 23:40 ` Janos Toth F.
2017-08-14 14:12 ` Goffredo Baroncelli
2017-08-14 19:28 ` Chris Murphy
2017-08-14 20:18 ` Goffredo Baroncelli
2017-08-14 21:10 ` Chris Murphy
2017-08-14 13:23 ` Austin S. Hemmelgarn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2aac70ec-cef4-3b5d-b4ef-7b6d94c32489@gmail.com \
--to=ahferroin7@gmail.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).