All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Billy Crook <billycrook@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: reshape raid5 to raid6
Date: Fri, 26 Jun 2009 12:00:02 +1000	[thread overview]
Message-ID: <19012.11170.110416.705413@notabene.brown> (raw)
In-Reply-To: message from Billy Crook on Wednesday June 24

On Wednesday June 24, billycrook@gmail.com wrote:
> On Wed, Jun 24, 2009 at 06:20, NeilBrown<neilb@suse.de> wrote:
> > On Wed, June 24, 2009 8:27 pm, Michael Ole Olsen wrote:
> >> Is it possible to reshape my /dev/md0 raid5 into raid6?
> >
> > If you are are using Linux 2.6.30, then you can
> >
> >  echo raid6 > /sys/block/md0/md/level
> >
> > and it will instantly be sort-of-raid6.
> > It is exactly like raid6 except that the Q blocks are all one
> > the one drive, and drive that previously didn't exist.
> > If you have a spare, it will start building the Q blocks
> > on that drive and when it finishes you will have true raid6
> > redundancy, though possibly a little less than raid6 performance,
> > as a real raid6 has the Q block distributed.
> >
> > When mdadm-3.1 is released, you will be able to tell the raid6
> > to re-stripe with a more traditional layout.  This will take quite
> > a while, but you can continue to use the array (though a bit more
> > slowly) will it progresses.
> > Of course you don't need to do that step if you don't want to.
> 
> I have a raid5 array on 2.6.18 that I'd like to grow like this.  I
> might wait until mdadm-3.1 so I can stripe Q from the git-go.  I'd
> like to --stop the array on the 2.6.18 machine, and export the
> individual disks over iscsi to a 2.6.30 machine, and use the newer
> mdadm there to grow the array from raid5 to raid6.  Then --stop it on
> the 2.6.30 machine, unexport the disks, and --start the array again on
> the 2.6.18 machine.  Disclaimers aside, should that work?  My main
> concern is 2.6.18's ability to work with this 'creative' raid6
> implementation that currently results from the grow from raid5 to
> raid6.

2.6.18 will not understand the raid6 created by simply echoing 'raid6'
in to the 'level' file.  It will need to be restriped with the help of
mdadm-3.1 first.

> 
> I've also got a few disks to add, so maybe the better solution would
> be to add one and get the unstriped Q, then add another and let Q
> stripe with everything else during the reshape.  That is, if it will
> stripe Q during the reshape.

Your best bet would be to wait for mdadm-3.1 and do it all at once,
something like:
  mdadm --grow /dev/md0 --level=raid6 --raid-disks=8

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-26  2:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 10:27 reshape raid5 to raid6 Michael Ole Olsen
2009-06-24 11:20 ` NeilBrown
     [not found]   ` <aebf5d970906240515y6c616250lca1cedea32927b00@mail.gmail.com>
2009-06-24 12:17     ` Beolach
2009-07-09  8:36       ` Mikael Abrahamsson
2009-07-09  9:35         ` NeilBrown
2009-06-24 13:32   ` Michael Ole Olsen
2009-06-24 16:10   ` Billy Crook
2009-06-26  2:00     ` Neil Brown [this message]
2009-07-15  3:29       ` Michael Ole Olsen
2009-07-15  3:58         ` NeilBrown

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=19012.11170.110416.705413@notabene.brown \
    --to=neilb@suse.de \
    --cc=billycrook@gmail.com \
    --cc=linux-raid@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 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.