From: NeilBrown <neilb@suse.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Gordon Henderson <gordon@drogon.net>, linux-raid@vger.kernel.org
Subject: Re: Raid 5 to Raid 1 (half of the data not required)
Date: Wed, 24 Aug 2011 18:42:35 +1000 [thread overview]
Message-ID: <20110824184235.2a165066@notabene.brown> (raw)
In-Reply-To: <alpine.DEB.2.00.1108241018180.4709@uplift.swm.pp.se>
On Wed, 24 Aug 2011 10:21:32 +0200 (CEST) Mikael Abrahamsson
<swmike@swm.pp.se> wrote:
> On Wed, 24 Aug 2011, Gordon Henderson wrote:
>
> > This isn't as "glamorous" as Neils method involving lots of mdadm
> > commands, shrinks and grows, but sometimes it's good to keep things at a
> > simpler level?
>
> Another way would be to add the new raid1 with missing drive to the lv,
> and pvmove all extents off of the existing raid5 md pv, then vgreduce away
> from it, stop the raid5, zero-superblock, and add one drive to add
> redundancy for the raid1.
>
> But that has little to do with linux raid, and all to do with LVM. It also
> means you can do everything online since pvmove doesn't require to offline
> anything.
>
There are certainly lots of approaches. :-)
But every approach will require either coping or shrinking the filesystem and
as extX doesn't support online shrinking the filesystem will have to be
effectively off-line while that shrink happens.
(if you shrink by coping, then it could be technically on-line but it had
better not be written to).
NeilBrown
next prev parent reply other threads:[~2011-08-24 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 23:41 Raid 5 to Raid 1 (half of the data not required) Mike Viau
2011-08-24 0:46 ` NeilBrown
[not found] ` <BAY148-W29A568212EC52E4C4BC52EF110@phx.gbl>
2011-08-24 2:39 ` NeilBrown
2011-08-24 7:34 ` Robin Hill
2011-08-24 8:03 ` Gordon Henderson
2011-08-24 8:21 ` Mikael Abrahamsson
2011-08-24 8:42 ` NeilBrown [this message]
2011-08-26 0:11 ` Mike Viau
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=20110824184235.2a165066@notabene.brown \
--to=neilb@suse.de \
--cc=gordon@drogon.net \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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).