From: NeilBrown <neilb@suse.de>
To: Steven Haigh <netwiz@crc.id.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 -> RAID6 conversion, please help
Date: Wed, 11 May 2011 10:21:16 +1000 [thread overview]
Message-ID: <20110511102116.494bf0fd@notabene.brown> (raw)
In-Reply-To: <4DC9CCAF.9010709@crc.id.au>
On Wed, 11 May 2011 09:39:27 +1000 Steven Haigh <netwiz@crc.id.au> wrote:
> On 11/05/2011 9:31 AM, NeilBrown wrote:
> > When it finished you will have a perfectly functional RAID6 array with full
> > redundancy. It might perform slightly differently to a standard layout -
> > I've never performed any measurements to see how differently.
> >
> > If you want to (after the recovery completes) you could convert to a regular
> > RAID6 with
> > mdadm -G /dev/md0 --layout=normalise --backup=/some/file/on/a/different/device
> >
> > but you probably don't have to.
> >
>
> This makes me wonder. How can one tell if the layout is 'normal' or with
> Q blocks on a single device?
>
> I recently changed my array from RAID5->6. Mine created a backup file
> and took just under 40 hours for 4 x 1Tb devices. I assume that this
> means that data was reorganised to the standard RAID6 style? The
> conversion was done at about 4-6Mb/sec.
Probably.
What is the 'layout' reported by "mdadm -D"?
If it ends -6, then it is a RAID5 layout with the Q block all on the last
disk.
If not, then it is already normalised.
>
> Is there any effect on doing a --layout=normalise if the above happened?
>
Probably not.
NeilBrown
next prev parent reply other threads:[~2011-05-11 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 23:15 RAID5 -> RAID6 conversion, please help Peter Kovari
2011-05-10 23:31 ` NeilBrown
2011-05-10 23:39 ` Steven Haigh
2011-05-11 0:21 ` NeilBrown [this message]
2011-05-11 0:38 ` Dylan Distasio
2011-05-11 0:47 ` NeilBrown
2011-05-11 1:04 ` Dylan Distasio
2011-05-11 3:29 ` NeilBrown
2011-05-11 0:08 ` Peter Kovari
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=20110511102116.494bf0fd@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=netwiz@crc.id.au \
/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).