Linux LVM users
 help / color / mirror / Atom feed
From: Eric Hopper <hopper@omnifarious.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] which files, which physical volumes?
Date: Sun, 26 Sep 2004 13:27:57 -0700	[thread overview]
Message-ID: <20040926202757.GG32455@omnifarious.org> (raw)
In-Reply-To: <4153BF33.6030008@myself.gen.nz>

[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

On Fri, Sep 24, 2004 at 06:31:15PM +1200, Steve Wray wrote:
> So is there any other way to decomission that physical volume that
> doesn't involve pvmove?

I end up using lvcreate (with some options) to create a new logical
volume that has no extents on the physical volume you want to move off
of, and has the exact same number of extents as the logical volume you
want to move.  Then use dd to copy the blocks from the filesystem you
want to move (which has to be unmounted, or mounted read-only) onto the
new one.  Then unmount the old one, lvremove it, and change fstab and
things so the new one is mounted in its place.

It's ugly and stupid.  But, since pvmove doesn't seem to work yet, I
think that's the best that can be done.  I'm sorely disappointed that
LVM2 was even put into the production kernel without pvmove working.
:-(

I know LVM2 and the device mapper concept are much better than LVM1.
But, pvmove is a core piece of functionality.  It's like releasing a
filesystem for which the lstat call doesn't work or something similar.

*sigh*,
-- 
"It does me no injury for my neighbor to say there are twenty gods or no God.
It neither picks my pocket nor breaks my leg."  --- Thomas Jefferson
"Go to Heaven for the climate, Hell for the company."  -- Mark Twain
-- Eric Hopper (hopper@omnifarious.org  http://www.omnifarious.org/~hopper) --

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-09-26 20:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  2:29 [linux-lvm] which files, which physical volumes? Steve Wray
2004-09-24  6:17 ` Luca Berra
2004-09-24  6:31   ` Steve Wray
2004-09-25 16:20     ` Clint Byrum
2004-09-25 16:50       ` Alasdair G Kergon
2004-09-25 22:05       ` Steve Wray
2004-09-26 23:49         ` Michael T. Babcock
2004-09-26 20:27     ` Eric Hopper [this message]
2004-09-26 20:38       ` Steve Wray
2004-09-27  0:30       ` Alasdair G Kergon
2004-09-27  7:58         ` Steve Wray
2004-09-24 19:00 ` John Stoffel

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=20040926202757.GG32455@omnifarious.org \
    --to=hopper@omnifarious.org \
    --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