vgextend output: Not enough physical extents per physical volume

[Pete Randall]

It says it was successfully extended, though. Does a current vgdisplay show more than 2169 PE's?

Pete

[Pete Randall]

Looks fine to me - it shows you've got two PV's. you've got 2169 free PE's on the second volume. Go with it.


Pete

[Helen French]

Just wondering the actual size of the disks? Are they same? Are they same type of hard disks? different vendor?

[Michael Steele_2 · Accepted solution]

One PE will be used for the LVM header.

#pvcreate -B -f /dev/rdsk/c0t8d0
#mkboot /dev/rdsk/c0t8d0
#mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c0t8d0
#vgextend /dev/vg00 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol4 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol5 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol6 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol7 /dev/dsk/c0t8d0
#lvextend -m 1 /dev/vg00/lvol8 /dev/dsk/c0t8d0
#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -d /dev/vg00/lvol2
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot ???R
#set_boot ???a HW_PATH

[Glenn Mitchell_4]

Same type of HD, same size, same vendor:

disk 0 8/12.5.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/12.8.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0

[Helen French]

Normally when you extend the VG with a bigger capacity disk, it would give warnings and error messages since the VG parameters (like PE size, Max PE per PV etc) have been set with the smaller capacity disks. In your case the PV size will be limited to 8676MB (Max PE per PV x PE size). 2169*4 = 8676MB. So, I would assume that the new HDD might have tried to set more PEs and failed to do so. This should not happen on same capacity disks though.

If you suspect any issues, remove disk, pvcreate it and add again. Check the output of diskinfo too.

[Michael Steele_2]

Please bear in mind that 1 PE will contain the VGRA.

If you've used the -B option with pvcreate then your bootlif was also successfully created.

From above vgdisplay vg looks fine.

If you want to check your bootlif use the lifls and lifcp commands.

lifls -C /dev/rdsk/c0t8d0

-and-

lifcp /dev/rdsk/c0t8d0:AUTO -

[Marco Santerre]

Basically what happened here is that your disk got defined with 2170 Physical Extents. Your VG on the other hand can only accomodate 2169 PE per Volumes. The message you got is basically telling you that it can only use 2169 PE of 2170 PE from your disk. In this case, I would disregard the message and just go along with it. If you try adding bigger capacity disks though, I would certainly look into recreating the VG with a bigger Max PE.

[Pradeep_3]

As Marco correctly said have you set max PE value while creating VG? If so whenever you get down time take ignite backup of vg00, remove vg00 and re-restore ignite backup so that in future also if you add disk of higher capacity you will not be able to use more than 2169 PE.