From: Neil Brown <neilb@suse.de>
To: CaT <cat@zip.com.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid5 resizing
Date: Wed, 19 Dec 2007 22:59:41 +1100 [thread overview]
Message-ID: <18281.1965.40403.734289@notabene.brown> (raw)
In-Reply-To: message from CaT on Wednesday December 19
On Wednesday December 19, cat@zip.com.au wrote:
> Hi,
>
> I'm thinking of slowly replacing disks in my raid5 array with bigger
> disks and then resize the array to fill up the new disks. Is this
> possible? Basically I would like to go from:
>
> 3 x 500gig RAID5 to 3 x 1tb RAID5, thereby going from 1tb to 2tb of
> storage.
>
> It seems like it should be, but... :)
Yes.
mdadm --grow /dev/mdX --size=max
NeilBrown
next prev parent reply other threads:[~2007-12-19 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 11:17 raid5 resizing CaT
2007-12-19 11:59 ` Neil Brown [this message]
2007-12-19 12:23 ` CaT
-- strict thread matches above, loose matches on Subject: below --
2006-05-01 5:23 CaT
2006-05-01 5:33 ` Neil Brown
2006-05-01 12:28 ` Mike Hardy
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=18281.1965.40403.734289@notabene.brown \
--to=neilb@suse.de \
--cc=cat@zip.com.au \
--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;
as well as URLs for NNTP newsgroup(s).