All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Oliver Martin <oliver@volatilevoid.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Creating a 3-disk RAID6 array
Date: Thu, 17 May 2012 21:36:12 -0500	[thread overview]
Message-ID: <4FB5B59C.2070402@hardwarefreak.com> (raw)
In-Reply-To: <4FB4534A.5070608@volatilevoid.net>

On 5/16/2012 8:24 PM, Oliver Martin 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.
> 
> 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.

Make a 3 partition (seems you're using partitions) md RAID 10 (RAID 1E)
array with what you have now.  When you add a disk down the road, backup
your filesystem, create your 4 disk md RAID 6 array, format, restore.

Now for my $0.02:  You're better served all around with a 4 partition
RAID 10 or 1+0, than a 4 partition RAID 6.  Random write performance is
greatly superior, rebuild time is significantly lower, etc.  Sure it
would be nice if mdadm could reshape a 3 disk RAID10 into a 4 disk
RAID10, but it can't.  But since you should be doing a backup/restore
anyway, it doesn't matter.

-- 
Stan

      parent reply	other threads:[~2012-05-18  2:36 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
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 [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=4FB5B59C.2070402@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.