From: Goswin von Brederlow <goswin-v-b@web.de>
To: Neil Brown <neilb@suse.de>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: Why do I need 4 disks for a raid6?
Date: Fri, 20 Mar 2009 11:20:42 +0100 [thread overview]
Message-ID: <87r60sv6kl.fsf@frosties.localdomain> (raw)
In-Reply-To: <18882.54987.332211.49180@notabene.brown> (Neil Brown's message of "Fri, 20 Mar 2009 10:35:39 +1100")
Neil Brown <neilb@suse.de> writes:
> In 2.6.30 and later you wont even need the downtime. Just
> echo raid5 > /sys/block/md9/md/level
> in place of the "stop" and "create" steps.
Hurray. It is great to see the raid driver improving all the
time. Great work all of you.
>> Now for the raid6 case. With only 1 data disk and 2 parity disks all 3
>> disks should end up with identical data on them. In effect this should
>> be a 3 disk raid1, a cpu intensive one. Take an existing raid1 with 2
>> or 3 disks, stop the raid, create a new raid6 ovver it with
>> --assume-clean, start the raid. After that one can add more disks and
>> --grow -n 4/5/6/.. the raid6 to a sensible size. Again without going
>> into degraded mode.
>>
>>
>> So back to my original question: Why does the kernel require 4 disks
>> for a raid6 instead of allowing 3?
>
> I have occasionally wondered that. But I didn't write that code and
> never saw a need to change it. As Andre says, it is very likely that
> just relaxing the restriction will allow it to "just work".
>
> Maybe that will happen in 2.6.31...
>
> NeilBrown
Time for try&error. I only checked one raid6 algorithm but that seemed
to be fine with 3 disks.
MfG
Goswin
next prev parent reply other threads:[~2009-03-20 10:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 19:12 Why do I need 4 disks for a raid6? Goswin von Brederlow
2009-03-18 3:41 ` david.geib
2009-03-18 9:50 ` Goswin von Brederlow
2009-03-18 18:12 ` david.geib
2009-03-18 12:18 ` Andre Noll
[not found] ` <49C0EA5F.9070901@vshift.com>
2009-03-18 12:35 ` Andre Noll
2009-03-18 14:08 ` Goswin von Brederlow
2009-03-18 14:26 ` Robin Hill
2009-03-18 18:48 ` Goswin von Brederlow
2009-04-01 16:08 ` H. Peter Anvin
2009-04-01 17:47 ` Andre Noll
2009-04-01 20:36 ` H. Peter Anvin
2009-04-01 18:07 ` Goswin von Brederlow
2009-04-01 19:05 ` H. Peter Anvin
2009-03-19 23:35 ` Neil Brown
2009-03-20 10:20 ` Goswin von Brederlow [this message]
2009-03-23 20:20 ` Nifty Fedora Mitch
2009-03-24 19:32 ` Goswin von Brederlow
2009-04-01 16:09 ` H. Peter Anvin
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=87r60sv6kl.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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