From: Stirling Westrup <swestrup@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Need help with a particular use-case for pvmove.
Date: Sat, 13 Nov 2010 22:56:05 -0500 [thread overview]
Message-ID: <AANLkTinXXW_QFHa7wEM-rb8rvO-8iXmAzK3yEL1j79uL@mail.gmail.com> (raw)
In-Reply-To: <20101113230310.GH14546@barkeeper1-xen.linbit>
On Sat, Nov 13, 2010 at 6:03 PM, Lars Ellenberg
<lars.ellenberg@linbit.com> wrote:
> On Sat, Nov 13, 2010 at 04:45:36PM -0500, Stirling Westrup wrote:
...
>> All I want to do is move physical extents from one physical volume to
>> another. Both of those volumes are present and accessible. Why should
>> uninvolved missing volumes be an issue, and is there any way around
>> it? �pmmove suggests running "vgreduce --removemissing" but the
>> documentation for vgreduce seems to say that I'd need to 1) use
>> --force and 2) it would likely result in data loss.
>>
>> Is there anything I can do, short of borrowing another storage array
>> somewhere, just so I can have an extra slot to do this move? My other
>> option is to put the new drive into a USB case, but the server only
>> supports USB1, so moving a terrabyte will take over a week.
>>
> If you do it offline anyways:
>
> Shut down.
> Unplug one of the good old drives, plug in the new drive.
> If you want to be extra sure against typos,
> unplug all but the bad-old drive ;-)
>
> Boot into maintenance mode, use a live-cd if you have to.
>
> Don't activate the VG. �It won't activate with one pv missing anyways,
> unless you really want it to.
>
> Then dd_rescue copy the disk image from bad-old to new, including
> everything (partition table, if any, LVM signature, the full image).
>
> Remove bad-old drive, have all other old and the new plugged,
> reboot normally.
>
> Done.
>
> Estimated downtime, assuming a sustained linear write speed of 80 MiB/s:
> 1 TiB / (80 MiB/s), well under 4 hours.
>
Thanks. I did consider this, but the new drive is twice the size of
the old one, so I would need to make sure I had created a partition on
the new drive the exact size of the old one, and had dd-ed everything
correctly. Even then, I wasn't sure if it would work, because I don't
know what the metadata records in terms of the drive configurations.
--
Stirling Westrup
Programmer, Entrepreneur.
https://www.linkedin.com/e/fpf/77228
http://www.linkedin.com/in/swestrup
http://technaut.livejournal.com
next prev parent reply other threads:[~2010-11-14 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 21:45 [linux-lvm] Need help with a particular use-case for pvmove Stirling Westrup
2010-11-13 23:03 ` Lars Ellenberg
2010-11-14 3:56 ` Stirling Westrup [this message]
2010-11-14 21:58 ` Lars Ellenberg
2010-11-14 23:52 ` Stirling Westrup
2010-11-14 22:56 ` Stuart D Gathman
2010-11-14 3:57 ` Stirling Westrup
2010-11-14 23:05 ` Stuart D Gathman
2010-11-13 23:22 ` Ray Morris
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=AANLkTinXXW_QFHa7wEM-rb8rvO-8iXmAzK3yEL1j79uL@mail.gmail.com \
--to=swestrup@gmail.com \
--cc=linux-lvm@redhat.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).