pvmove: failure possibly caused by strict allocation policy

[Matt (A) Speroni]

Hi everyone,

I'm having some problems to complete the pvmove, when I try to run it I got the following message and the operation fails.
There seems that there's a kind of problem with the strict policy but I'm not quit sure of that, the OS is 11.23 on rx series.


pvmove /dev/dsk/c21t2d6 /dev/dsk/c19t1d4
pvmove: Not enough free physical extents available.
Logical volume "/dev/vg_db/lvdata01" could not be extended.
pvmove: Cannot find a free physical extent for logical extent 13245
of logical volume "/dev/vg_db/lvdata01".
Failure possibly caused by strict allocation policy

pvdisplay -v /dev/dsk/c21t2d6

--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg_db/lvdata01 14062 14062

--- Physical extents ---
PE Status LV LE
00000 current /dev/vg_db/lvdata01 13245
00001 current /dev/vg_db/lvdata01 13246
00002 current /dev/vg_db/lvdata01 13247
00003 current /dev/vg_db/lvdata01 13248
00004 current /dev/vg_db/lvdata01 13249
00005 current /dev/vg_db/lvdata01 13250


pvdisplay -v /dev/dsk/c19t1d4

00959 current /dev/vg_db/lvdata01 00959
00960 current /dev/vg_db/lvdata01 00960
00961 current /dev/vg_db/lvdata01 13245
00962 free 00000
00963 free 00000
00964 free 00000
00965 free 00000
00966 free 00000


# lvdisplay /dev/vg_db/lvdata01
--- Logical volumes ---
LV Name /dev/vg_db/lvdata01
VG Name /dev/vg_db
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 218456
Current LE 27307
Allocated PE 27307
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation strict
IO Timeout (Seconds) default

[Prashanth Waugh]

Hi Matias,
pvmove succeeds only if there is enough space on the destination physical volumes to hold all the allocated extents of the source physical volume.

Regards
Prashant

[Prashanth Waugh]

Hi ,

Check the size using diskinfo
#diskinfo /dev/rdsk/c19t1d4
#diskinfo /dev/rdsk/c21t2d6

Regards
Prashant

[Prashanth Waugh]

Hi,

pvmove possible in the same VG only. while doing pvmove VG shouldnot be active in shared mode.

Regards
Prashant

[Matt (A) Speroni]

Thanks Prashant,

This is the scenario, there is enough space in the target PV, besides there are enough PE/LE too to complete this task, therefore I guess that certainly there are some kind of restriction or some bad configuration in the VG.
Btw, these PVs belongs to the same VG and as u can see below, there's enough PE free to reallocate the data.
# pvdisplay /dev/dsk/c21t2d6
--- Physical volumes ---
PV Name /dev/dsk/c21t2d6
PV Name /dev/dsk/c17t2d6 Alternate Link
VG Name /dev/vg_db
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 8
Total PE 30715
Free PE 16653
Allocated PE 14062
Stale PE 0
IO Timeout (Seconds) 90
Autoswitch On
Proactive Polling On

# pvdisplay /dev/dsk/c19t1d4
--- Physical volumes ---
PV Name /dev/dsk/c19t1d4
PV Name /dev/dsk/c15t1d4 Alternate Link
VG Name /dev/vg_db
PV Status available
Allocatable yes
VGDA 2
Cur LV 2
PE Size (Mbytes) 8
Total PE 31995
Free PE 26618
Allocated PE 5377
Stale PE 0
IO Timeout (Seconds) 90
Autoswitch On
Proactive Polling On

[SKR_1]

Please provide vgdisplay -v vgname output.

Thanks

SKR

[Matt (A) Speroni]

# vgdisplay -v /dev/vg_db
--- Volume groups ---
VG Name /dev/vg_db
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 5
Open LV 5
Max PV 16
Cur PV 10
Act PV 10
Max PE per PV 31999
VGDA 20
PE Size (Mbytes) 8
Total PE 287954
Alloc PE 143980
Free PE 143974
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg_db/lvdata06
LV Status available/syncd
LV Size (Mbytes) 238304
Current LE 29788
Allocated PE 29788
Used PV 1

LV Name /dev/vg_db/lvdata01
LV Status available/syncd
LV Size (Mbytes) 238304
Current LE 29788
Allocated PE 29788
Used PV 2

LV Name /dev/vg_db/lvdata02
LV Status available/syncd
LV Size (Mbytes) 238304
Current LE 29788
Allocated PE 29788
Used PV 2

LV Name /dev/vg_db/lvdata03
LV Status available/syncd
LV Size (Mbytes) 218456
Current LE 27307
Allocated PE 27309
Used PV 3

LV Name /dev/vg_db/lvdata04
LV Status available/syncd
LV Size (Mbytes) 218456
Current LE 27307
Allocated PE 27307
Used PV 3


--- Physical volumes ---
PV Name /dev/dsk/c21t1d2
PV Name /dev/dsk/c17t1d2 Alternate Link
PV Status available
Total PE 31995
Free PE 2207
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c19t1d4
PV Name /dev/dsk/c15t1d4 Alternate Link
PV Status available
Total PE 31995
Free PE 26618
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c21t1d6
PV Name /dev/dsk/c17t1d6 Alternate Link
PV Status available
Total PE 31995
Free PE 6622
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c19t2d0
PV Name /dev/dsk/c15t2d0 Alternate Link
PV Status available
Total PE 31995
Free PE 23165
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c21t2d2
PV Name /dev/dsk/c17t2d2 Alternate Link
PV Status available
Total PE 31995
Free PE 11037
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c19t2d4
PV Name /dev/dsk/c15t2d4 Alternate Link
PV Status available
Total PE 31995
Free PE 19710
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c21t2d6
PV Name /dev/dsk/c17t2d6 Alternate Link
PV Status available
Total PE 30715
Free PE 16653
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c19t3d0
PV Name /dev/dsk/c15t3d0 Alternate Link
PV Status available
Total PE 17277
Free PE 10654
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c21t3d2
PV Name /dev/dsk/c17t3d2 Alternate Link
PV Status available
Total PE 15997
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c19t1d0
PV Name /dev/dsk/c15t1d0 Alternate Link
PV Status available
Total PE 31995
Free PE 27308
Autoswitch On
Proactive Polling On

[SKR_1]

Hi,

Your VG is not looking in shared mode. First take the backup of Volume group. Then you can run below commands.

pvmove -n lvdata01 /dev/dsk/c21t2d6 /dev/dsk/c19t1d4

Thanks

SKR