On Sat, Sep 19, 2009 at 03:18:41PM +0200, Elrond wrote:
> Moving inside the same PV (for example to reduce
> fragmentation) does not seem to be supported at all. I
> usually have to do that by moving the PEs first to another
> PV and then back.
--alloc anywhere
Alasdair
--
a...@redhat.com
--
Hi,
I experienced nearly exactly the same problem two days ago.
Also with *.44.
One big difference in my case:
I used a failing pvmove first:
pvmove -v -i 10 /dev/sda6:0-20 /dev/sda6:100-120
Moving inside the same PV (for example to reduce
fragmentation) does not seem to be supported a
Hi,
Alasdair G Kergon wrote:
> For pvmove completing when it hadn't actually moved, you need a bug fix:
> Fix pvmove to revert operation if temporary mirror creation fails.
> which is in 2.02.47 upstream that I'll be releasing in a few hours.
> (It's actually in 2.02.46 I released the other
For pvmove completing when it hadn't actually moved, you need a bug fix:
Fix pvmove to revert operation if temporary mirror creation fails.
which is in 2.02.47 upstream that I'll be releasing in a few hours.
(It's actually in 2.02.46 I released the other day, but I've withdrawn that
release due
Package: lvm2
Version: 2.02.44-3
Severity: important
Hi,
I had a VG (aya) on two PV (sda2 and sdd1) that I want to move to another
disk. So I create a new PV on hdb3, add it in VG aya and then I use pvmove.
the sda2 PV only contained one LV (aya/root, the root fs of the machine) and
sdd1 PV o
5 matches
Mail list logo
