From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid@vger.kernel.org
Subject: Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
Date: Mon, 01 Dec 2014 09:42:10 +0000 [thread overview]
Message-ID: <547C37F2.1030400@youngman.org.uk> (raw)
In-Reply-To: <20141201090814.GA3772@cthulhu.home.robinhill.me.uk>
On 01/12/14 09:08, Robin Hill wrote:
> If it is doable (see comment above), it'll be simpler to just
> partition the disks to the final size (or skip partitioning at all)
> - md will quite happily accept larger devices added to an array
> (though it doesn't use the extra space). Otherwise, your initial
> steps are correct - though if you have a spare bay (or even a
> USB/SATA adapter), you can add the drive as a spare and then use
> "mdadm --replace" (you may need a newer version of mdadm for this)
> command to flag one of the existing array members for replacement.
> This will do a direct copy of the data from the existing disk to
> the new one and is quicker (and safer) than fail/add.
I upgraded a (raid 1) system by just adding the new, larger, disk. I
think I swapped a 500Gb for a 1TB, so replaced my 400Gb partitions
with 900Gb partitions. I then grew the array, followed by growing the
partition. Worked fine.
Cheers,
Wol
prev parent reply other threads:[~2014-12-01 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 2:55 upgrading a RAID array in-place with larger drives. request for review of my approach? terrygalant
2014-12-01 3:28 ` John Stoffel
2014-12-01 4:04 ` terrygalant
2014-12-01 13:47 ` Phil Turmel
2014-12-01 9:08 ` Robin Hill
2014-12-01 9:42 ` Wols Lists [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=547C37F2.1030400@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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).