Bug#406454: closed by Bastian Blank <firstname.lastname@example.org> (Re:
Bug#406454: pvmove: fails to move within the same physical volume)
Goswin von Brederlow
brederlo at informatik.uni-tuebingen.de
Thu Jan 11 15:59:36 UTC 2007
Reopening as wishlist. There is no reason pvmove should not be able
to do this.
> From: Bastian Blank <waldi at debian.org>
> Subject: Re: Bug#406454: pvmove: fails to move within the same physical volume
> To: 406454-done at bugs.debian.org
> Date: Thu, 11 Jan 2007 11:46:34 +0100
> On Thu, Jan 11, 2007 at 10:37:24AM +0100, Goswin von Brederlow wrote:
>> I'm trying to move a logical volume within in single physical volume but pvmove claims there are no available extends:
> No bug. The documentation stats:
> | pvmove allows you to move the allocated physical extents (PEs) on
> | SourcePhysicalVolume to one or more other physical volumes (PVs).
That should be made clearer then in both the manpage and the error
message. If pvmove can't move PEs on the same PV then it should check
that they differ and complain about it specifically.
> You can force it to move PE within one PV with --alloc anywhere or so.
The --alloc parameter is not documented outside the synopsis. What is
the 'AllocationPolicy' parameter? What values can it hold and what
value do I need to move withint a PV?
If --alloc .... allows to move within a PE then pvmove should
automatically use that setting when it detects that source PE and Dest
PE are the same. Maybe with the restriction that the Dest PE must have
a starting PE or full PE-PE range.
More information about the pkg-lvm-maintainers