[linux-lvm] which files, which physical volumes?
steve at myself.gen.nz
Sun Sep 26 20:38:09 UTC 2004
Eric Hopper wrote:
> 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.
Unfortunately I don't have enough disk for this... nice idea though!
> 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.
Phew! At least I am not the only one who feels like that!
This is for my home system, but at work, since discovering the
non-workingness of pvmove, I have tried to make sure that we don't have
to use it...
> 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.
Absolutely. I am actually amazed that its still like this after so long.
I mean, whats the problem? Is Redhat blocking it somehow or what?
(I sort of sniff a scenario where Redhat have some proprietary volume
management system in the pipeline and want to discourage people from
using LVM2 so that they will be more likely to but into Redhat
Enterprise Server or whatever, but maybe thats just paranoia speaking
and I should just take the tinfoil hat off and let the rays in)
More information about the linux-lvm