pvmove: not enough free physical extents available

[Coolmar]

hi,

We have to modify a volume group. In order to do this we have to free up PE 0. We followed the instructions which said to do the following:
# pvmove /dev/dsk/c4t0d4:0 /dev/dsk/c4t0d4

which gave the following error:
pvmove: Not enough free physical extents available.

We removed the strict allocation policies on the LVs and that didn't help either.

Any suggestions?

HP-UX 11.23

# vgdisplay /dev/vgqac
--- Volume groups ---
VG Name /dev/vgqac
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 24
Open LV 24
Max PV 16
Cur PV 9
Act PV 9
Max PE per PV 20000
VGDA 18
PE Size (Mbytes) 4
Total PE 104424
Alloc PE 102207
Free PE 2217
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

[Coolmar]

- Sorry, I should have added the following:

--- Logical volumes ---
LV Name /dev/vgqac/lvarch
VG Name /dev/vgqac
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 1024
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c4t0d4 1024 1024

[Coolmar]

So pvmove will move extent 0 to a free extent on the same PV. However, it looks like I don't have any free extents. Can I move extent 0 to ANY free extent on any PV in the VG?

[Matti_Kurkela]

I can't see why not.

Since you're planning to use vgmodify, you've no doubt already made a full backup. So go ahead, try it out.

MK

[James R. Ferguson]

Hi :

> So pvmove will move extent 0 to a free extent on the same PV. However, it looks like I don't have any free extents. Can I move extent 0 to ANY free extent on any PV in the VG?

The manpages indicate that "If a destination physical volume or physical volume group is not specified, all physical volumes in the
volume group are available as destination volumes for the transfer. pvmove selects the proper physical volumes to be used in order to preserve the allocation policies of the logical volume involved".

Regards!

...JRF...

[Coolmar]

I do also have 8GB free...so I was thinking of just adding a couple of extents to the LV and then trying the pvmove again to the same PV.

[James R. Ferguson]

Hi (again):

> I do also have 8GB free...so I was thinking of just adding a couple of extents to the LV and then trying the pvmove again to the same PV.

This isn't going to do anything. The logical volume doesn't "know" what's "used" and what's not. You need free *physical* extents on a physical volume (which you have somewhere in the volume group).

Regards!

...JRF...

[Sujit]

Coolmar,

When you run vgmodify cmd. it needs first PE on every disk in the VG must be free. I can see you have 9 PV in /dev/vgqac VG.

First you must see which PV has enough free space. For eg. we consider it as /dev/dsk/c4t0d9
#pvmove /dev/dsk/c4t0d4:0 /dev/dsk/c4t0d9

run above cmd for all disk in the VG including /dev/dsk/c4t0d9.
#pvmove /dev/dsk/c4t0d9:0 /dev/dsk/c4t0d9

After this you will be able to modify VG with vgmodify cmd.


Sujit.