From: David Brown <david.brown@hesbynett.no>
To: NeilBrown <neilb@suse.de>
Cc: Oliver Martin <oliver@volatilevoid.net>, linux-raid@vger.kernel.org
Subject: Re: Creating a 3-disk RAID6 array
Date: Thu, 17 May 2012 15:18:33 +0200 [thread overview]
Message-ID: <4FB4FAA9.7000100@hesbynett.no> (raw)
In-Reply-To: <20120517113817.7faf9c1e@notabene.brown>
On 17/05/12 03:38, NeilBrown wrote:
> On Thu, 17 May 2012 03:24:26 +0200 Oliver Martin<oliver@volatilevoid.net>
> wrote:
>
>> Hi,
>>
>> is there any specific reason why md refuses to create a RAID6 array with
>> 3 disks? My (probably naive) understanding suggests it should be the
>> same as a 3-disk RAID1, similar to a 2-disk RAID5.
>
> I'll have to leave for for hpa to answer. I've occasionally thought that
> maybe it should be fixed, but it never seemed worth the effort.
>
>>
>> The reason I'm asking is that I currently have space on three disks for
>> a new array, and would like to expand it when I add a fourth. I tried
>> this scenario with a few loopback devices, but the only way to go from a
>> 3-disk RAID1 to a 4-disk RAID6 seems to be via an intermediate 3-disk
>> RAID5, requiring two reshapes. I'd like to avoid one of them, if at all
>> possible.
>
> Yes, not possible at present.
> It might be as simple and finding the places that impose the limit and delete
> them...
>
> NeilBrown
>
Theoretically, a 3-disk RAID6 is like a 2-disk RAID5 or a 1-disk RAID1 -
it is possible, but not much use except as a building block for
expansion later. mdadm supports 1-disk RAID1 (you need a "--force" to
persuade mdadm that you know what you are doing, which is nice), and I
think it supports a 2-disk RAID5, though I haven't tried it. I can't
think of any good reason for it /not/ to support 3-disk RAID6, as there
is nothing in the algorithms to hinder it.
mvh.,
David
next prev parent reply other threads:[~2012-05-17 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 1:24 Creating a 3-disk RAID6 array Oliver Martin
2012-05-17 1:38 ` NeilBrown
2012-05-17 13:18 ` David Brown [this message]
2012-05-17 14:04 ` John Robinson
2012-05-18 7:24 ` David Brown
2012-05-18 7:30 ` H. Peter Anvin
2012-05-18 7:57 ` NeilBrown
2012-05-19 0:04 ` H. Peter Anvin
2012-05-17 21:02 ` Dan Williams
2012-05-17 23:27 ` Oliver Martin
2012-05-17 4:22 ` Bill Davidsen
2012-05-18 2:36 ` Stan Hoeppner
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=4FB4FAA9.7000100@hesbynett.no \
--to=david.brown@hesbynett.no \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=oliver@volatilevoid.net \
/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).