From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: Re: Using 2.6.31 liveCD to grow (reshape) raid5 into raid6, then bacck to old kernel?
Date: Fri, 13 Nov 2009 10:08:38 +0100 [thread overview]
Message-ID: <20091113100838.5ee6fc1d@atak.bl.pg.gda.pl> (raw)
In-Reply-To: <19196.57969.529323.360914@notabene.brown>
Neil Brown said: (by the date of Fri, 13 Nov 2009 15:37:05 +1100)
> > And so my plan is to get some liveCD with 2.6.31 (or maybe 2.6.32 ?).
> > Connect the sixth drive, boot liveCD, perform the migration:
> >
> > mdadm --add /dev/md2 /dev/sdd3
> > mdadm --grow /dev/md2 --level=raid6 --raid-disks=6
> >
> > Then reboot back into linux 2.6.24.
> >
> > Will this work?
>
> In principle, yes.
> However:
> 1/ you need linux 2.6.32 (not yet released). Don't try with 2.6.31
> 2/ you need mdadm 3.1.1 (not yet released). Don't try with 3.1,
> which has been withdrawn.
> 3/ You need a "--backup-file=/some/file" argument. The /some/file
> must be on a different device.
>
> >
> > Will 2.6.24 understand such raid6 ?
>
> Yes.
> mdadm will first convert the RAID5 to a RAID6 in which the Q blocks
> are all on the last disk. This is done instantly.
> Then mdadm will start and manage a process of re-laying out each
> stripe to have the Q blocks rotated around the various devices.
> This will take a while, approximately 1 day. Once this is complete,
> you can then access the array from 2.6.24.
>
> NeilBrown
Great, thanks a lot! I'm not in such a hurry - I will wait until they
are released.
--
Janek Kozicki |
prev parent reply other threads:[~2009-11-13 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 21:03 Using 2.6.31 liveCD to grow (reshape) raid5 into raid6, then bacck to old kernel? Janek Kozicki
2009-11-12 21:06 ` Janek Kozicki
2009-11-12 21:14 ` Robin Hill
2009-11-13 4:37 ` Neil Brown
2009-11-13 9:08 ` Janek Kozicki [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=20091113100838.5ee6fc1d@atak.bl.pg.gda.pl \
--to=janek_listy@wp.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox