linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: thomas@fjellstrom.ca
Cc: linux-raid@vger.kernel.org
Subject: Re: Backup file size when migrating from raid5 to raid6?
Date: Fri, 17 Aug 2012 10:39:26 +1000	[thread overview]
Message-ID: <20120817103926.78a37994@notabene.brown> (raw)
In-Reply-To: <201208161728.13814.thomas@fjellstrom.ca>

[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]

On Thu, 16 Aug 2012 17:28:13 -0600 Thomas Fjellstrom <thomas@fjellstrom.ca>
wrote:

> On Sun May 6, 2012, NeilBrown wrote:
> > On Mon, 7 May 2012 00:32:35 +0000 Garðar Arnarsson <gardar@giraffi.net> 
> wrote:
> > 
> > > That's an excellent idea, I was going to add another disk for extra space
> > > right after migrating to raid6.
> > > 
> > > Just to be clear, I'll be running the normalize attribute just once to
> > > straighten the array out right? Or will I have to do it for every extra
> > > drive I add in the future?
> > 
> > Just once.
> > 
> > > 
> > > And what are the N+1 you mention in --raid-devices=N+1
> > 
> > By "N+1" I just meant "1 more than the number of devices currently in the
> > array".
> > 
> > If you have both new devices ready to go, you just do a single reshape
> > operation that converts to RAID6 and adds more space.  This does not need a
> > backup file and is probably the best approach.
> > 
> > If you currently have a 10-drive RAID5 and want a 12-drive RAID6, then
> > 
> >  mdadm --grow /dev/md0 --raid-devices=12 --level=6
> > 
> > is what you want.
> 
> I apologize for bringing back a long dead thread, but I've been wondering if 
> mdadm does the grow op in this case, in one step? Or does it internally do 
> each step separately, doing a reshape with each one?
> 
> I've currently got a 7x1TB disk raid5, and have a couple more disks to add and 
> I was planning on moving to raid6. I'm hoping to reduce the amount of time the 
> array is "reshaping" because I'm a bit paranoid that my bad luck with hard 
> drives will decide to hit right then and there.
> 

If you change the level and the number of devices in the one command, and
there are already enough spares present to satisfy the requirements of the
new size, then it will only perform a single reshape operation which will use
the minimal amount of time.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-08-17  0:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH-e9vLTY2eo0p3ud5FaWNe_2f8hej0aitFuu8K0M1RZdObiXQ@mail.gmail.com>
2012-05-06 10:17 ` Backup file size when migrating from raid5 to raid6? Garðar Arnarsson
2012-05-06 11:00   ` NeilBrown
     [not found]     ` <CAH-e9vJkrv2R-HTR7JfHwZK1sbYQ3fduGbtxEwtor4gtyd6PKQ@mail.gmail.com>
2012-05-07  0:35       ` Garðar Arnarsson
2012-05-07  0:54       ` NeilBrown
2012-08-16 23:28         ` Thomas Fjellstrom
2012-08-17  0:39           ` NeilBrown [this message]
2012-08-17  0:45             ` Thomas Fjellstrom
2012-08-17  0:52           ` John Robinson
2013-07-17 13:01   ` Boyan Alexiev
2013-07-17 20:51     ` 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=20120817103926.78a37994@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomas@fjellstrom.ca \
    /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).