[linux-lvm] Problems with pvmove

[linux-lvm] Problems with pvmove

[Andreas Gorf]

I've followed the discussion started by „fejf“.

Indeed i have the same problem that pvmove exits with an error when i try 
to
move PEs from one PV to another.

To exclude the possibility of a defect HD i tried to reproduce the error 
on several
independent systems.

The error always occurs when i try to move a complete filled PV to 
another. In this case all but the last
PE on this PV are moved. The last one isn't movable whatever i did.

If the PV wasn't filled at 100% everything goes fine.

To reproduce the error try the following:

- create a VG with three Pvs at the same size
- create a LV which covers the first PV completely and the second partly
- try to all PEs from the first PV to the third - the error will occur
- move the moved PEs back to the first PV - everything goes fine
- try to move the PEs lying on the second PV to the third - everything 
goes fine


...any ideas?


Andreas...

Re: [linux-lvm] Problems with pvmove

[Heinz J . Mauelshagen]

Andreas,

could you provide a "pvdisplay -v | tail -22" output of the PV in question
in order to check if you suffer from a misalocation problem which would lead
to a last PE being allocated partially beyond the end of the underlying devive.

Regards,
Heinz    -- The LVM Guy --


On Sun, Sep 09, 2001 at 04:55:30PM +0000, Andreas Gorf wrote:
> I've followed the discussion started by „fejf“.
> 
> Indeed i have the same problem that pvmove exits with an error when i try 
> to
> move PEs from one PV to another.
> 
> To exclude the possibility of a defect HD i tried to reproduce the error 
> on several
> independent systems.
> 
> The error always occurs when i try to move a complete filled PV to 
> another. In this case all but the last
> PE on this PV are moved. The last one isn't movable whatever i did.
> 
> If the PV wasn't filled at 100% everything goes fine.
> 
> To reproduce the error try the following:
> 
> - create a VG with three Pvs at the same size
> - create a LV which covers the first PV completely and the second partly
> - try to all PEs from the first PV to the third - the error will occur
> - move the moved PEs back to the first PV - everything goes fine
> - try to move the PEs lying on the second PV to the third - everything 
> goes fine
> 
> 
> ...any ideas?
> 
> 
> Andreas...
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[linux-lvm] Problems with pvmove

[Nils Juergens]

Hi Folks,

i'v got a volume group with three physical volumes (see below for
details) and one logical volume in it. Now i want to remove one PV.

I try to empty the PV with

 > pvmove /dev/hdb5
 > pvmove -- moving physical extents in active volume group "meine_volumes"
 > pvmove -- WARNING: moving of active logical volumes may cause data loss!
 > pvmove -- do you want to continue? [y/n] y
 > pvmove -- ERROR reading input physical volume "/dev/hdb5"

 > pvmove -- ERROR "pv_move_pe(): read input PV" pv_move_pe

 > pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents

On the other hand - i was able to clear another PV (/dev/hdc5) from the
same PG with the above command and then remove it from the VG.

I'm using SuSEs 2.2.14-Kernel on a Debian 2.2 i386 with lvm-0.8final.

any ideas?

Nils

------------------------------------------------------------------------
--- Volume group ---
VG Name               meine_volumes
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               0
MAX LV Size           255.99 GB
Max PV                256
Cur PV                3
Act PV                3
VG Size               20.17 GB
PE Size               4 MB
Total PE              5163
Alloc PE / Size       3871 / 15.12 GB
Free  PE / Size       1292 / 5.05 GB

--- Physical volumes ---
PV Name (#)           /dev/hda5 (2)
PV Status             available / allocatable
Total PE / Free PE    2415 / 0

PV Name (#)           /dev/hdb5 (1)
PV Status             available / allocatable
Total PE / Free PE    503 / 60

PV Name (#)           /dev/hdc11 (3)
PV Status             available / allocatable
Total PE / Free PE    2245 / 1232

-- 
 >   Nils Juergens  | nils@muon.de | icq 7090774   <
 >    Yes, Sir. Deathmatch _is_ a marketing term   <
 >        for "online brainstorming session"       <