From: NeilBrown <neilb@suse.de>
To: lrhorer@satx.rr.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Growing a RAID array
Date: Fri, 13 May 2011 11:23:13 +1000 [thread overview]
Message-ID: <20110513112313.54fbb717@notabene.brown> (raw)
In-Reply-To: <28.92.03893.3038CCD4@cdptpa-omtalb.mail.rr.com>
On Thu, 12 May 2011 20:02:01 -0500 "Leslie Rhorer" <lrhorer@satx.rr.com>
wrote:
>
> I am shortly going to be growing a 10 drive RAID6 array with two
> additional drives. Can this be done in a single grow operation by setting
> n=12, or do I have to grow it 1 drive at a time?
>
Experiment with loop-back devices created on modest sized files.
(but yes, you can grow by any number you like. You should test the drives
fairly heavily first, because if they both die during the reshape, you lose
your data).
NeilBrown
next prev parent reply other threads:[~2011-05-13 1:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 1:02 Growing a RAID array Leslie Rhorer
2011-05-13 1:23 ` NeilBrown [this message]
2011-05-13 5:57 ` Leslie Rhorer
2011-05-14 7:17 ` Leslie Rhorer
2011-05-14 8:14 ` NeilBrown
2011-05-14 14:43 ` Leslie Rhorer
2011-05-14 16:44 ` Leslie Rhorer
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=20110513112313.54fbb717@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.com \
/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).