From: waxhead <waxhead@dirtcellar.net>
To: kreijack@inwind.it, Duncan <1i5t5.duncan@cox.net>,
linux-btrfs@vger.kernel.org
Subject: Re: RAID56 - 6 parity raid
Date: Wed, 2 May 2018 18:55:58 +0200 [thread overview]
Message-ID: <bf58f92b-4d38-91dc-e515-eef5ab969dde@dirtcellar.net> (raw)
In-Reply-To: <0931730f-be41-e63b-f7f9-85fd111d0470@libero.it>
Goffredo Baroncelli wrote:
> Hi
> On 05/02/2018 03:47 AM, Duncan wrote:
>> Gandalf Corvotempesta posted on Tue, 01 May 2018 21:57:59 +0000 as
>> excerpted:
>>
>>> Hi to all I've found some patches from Andrea Mazzoleni that adds
>>> support up to 6 parity raid.
>>> Why these are wasn't merged ?
>>> With modern disk size, having something greater than 2 parity, would be
>>> great.
>> 1) [...] the parity isn't checksummed, ....
>
> Why the fact that the parity is not checksummed is a problem ?
> I read several times that this is a problem. However each time the thread reached the conclusion that... it is not a problem.
>
> So again, which problem would solve having the parity checksummed ? On the best of my knowledge nothing. In any case the data is checksummed so it is impossible to return corrupted data (modulo bug :-) ).
>
I am not a BTRFS dev , but this should be quite easy to answer. Unless
you checksum the parity there is no way to verify that that the data
(parity) you use to reconstruct other data is correct.
> On the other side, having the parity would increase both the code complexity and the write amplification, because every time a part of the stripe is touched not only the parity has to be updated, but also the checksum has too..
Which is a good thing. BTRFS main selling point is that you can feel
pretty confident that whatever you put is exactly what you get out.
next prev parent reply other threads:[~2018-05-02 16:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 21:57 RAID56 - 6 parity raid Gandalf Corvotempesta
2018-05-02 1:47 ` Duncan
2018-05-02 16:27 ` Goffredo Baroncelli
2018-05-02 16:55 ` waxhead [this message]
2018-05-02 17:19 ` Austin S. Hemmelgarn
2018-05-02 17:25 ` Goffredo Baroncelli
2018-05-02 18:17 ` waxhead
2018-05-02 18:50 ` Andrei Borzenkov
2018-05-02 21:20 ` waxhead
2018-05-02 21:54 ` Goffredo Baroncelli
2018-05-02 19:04 ` Goffredo Baroncelli
2018-05-02 19:29 ` Austin S. Hemmelgarn
2018-05-02 20:40 ` Goffredo Baroncelli
2018-05-02 23:32 ` Duncan
2018-05-03 11:26 ` Austin S. Hemmelgarn
2018-05-03 19:00 ` Goffredo Baroncelli
2018-05-03 8:11 ` Andrei Borzenkov
2018-05-03 11:28 ` Austin S. Hemmelgarn
2018-05-03 12:47 ` Alberto Bursi
2018-05-03 19:03 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2018-05-02 19:25 Gandalf Corvotempesta
2018-05-02 23:07 ` Duncan
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=bf58f92b-4d38-91dc-e515-eef5ab969dde@dirtcellar.net \
--to=waxhead@dirtcellar.net \
--cc=1i5t5.duncan@cox.net \
--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