Scenario: There is a file system space, need to expand space, the preparation work found that the file system corresponding to the LV VG "free PE" value is 0,VG has no space, so to first expand the VG, and then expand the LV, but the expansion of the VG found "MAX PV" has reached the limit to increase PV, It is necessary to first increase the "MAX PV" specific information as follows:
#vgdisplay/dev/datavg
---Volume groups---
VG Name/dev/datavg
VG Write Access Read/write
VG Status Available
Max LV 255
Cur LV 1
Open LV 1
Max PV
Cur PV 20
Act PV
Max PE per PV 42000
VGDA 40
PE Size (Mbytes) 256
Total PE 40580
Alloc PE 40580
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs on use 0
VG Version 1.0
VG Max Size 210000g
VG Max Extents 840000
Found that this VG is in 1.0 version, so there are two ways to solve this problem, one is to modify "MAX PV" through Vgmodify, and the other is to upgrade the VG 1.0 expires 2.0, here is mainly about how VG 1.0 upgrade to 2.0.
Prepare before Upgrade:
Upgrade from VG1.0 to 2.0 to go to the datavg to activate, as long as the business involved in the VG, all need to stop;
Backup DATAVG related configuration information; it's better to back up all of the file system data that the VG is involved in case
Vgexport-p-v-s-M Datavg.map/dev/datavg
Vgcfgbackup/dev/datavg
Upgrade implementation:
Go ahead and mount all the file systems related to Datavg, then execute;
#vgchange-A N/dev/datavg
Volume Group "/dev/datavg" has been successfully changed.
#vgversion-V 2.0/dev/datavg
Performing "Vgchange-a y-l-p-s/dev/datavg" to collect data
Activated Volume Group.
Volume Group "/dev/datavg" has been successfully activated.
Warning:volume Group version 2.0 does not support bad block
Relocation. The bad block relocation policy of all logical volumes
'll is set to NONE.
Old Volume Group configuration for "/dev/datavg" have been saved in "/etc/lvmconf/vgversion_datavg/datavg_1.0.conf"
Deactivating Volume Group "/dev/datavg"
Volume Group "/dev/datavg" has been successfully deactivated.
New Volume Group configuration for "/dev/datavg" have been saved in "/etc/lvmconf/vgversion_datavg/datavg_2.0.conf"
Removing the Volume group/dev/datavg from/etc/lvmtab
Applying the configuration to all physical Volumes from "/etc/lvmconf/vgversion_datavg/datavg_2.0.conf"
Volume Group configuration has been restored TO/DEV/RDISK/DISK44
Volume Group configuration has been restored TO/DEV/RDISK/DISK43
Volume Group configuration has been restored TO/DEV/RDISK/DISK42
Volume Group configuration has been restored TO/DEV/RDISK/DISK41
Volume Group configuration has been restored TO/DEV/RDISK/DISK40
Volume Group configuration has been restored to/dev/rdisk/disk39
Volume Group configuration has been restored to/dev/rdisk/disk38
Volume Group configuration has been restored to/dev/rdisk/disk37
Volume Group configuration has been restored TO/DEV/RDISK/DISK36
Volume Group configuration has been restored TO/DEV/RDISK/DISK35
Volume Group configuration has been restored TO/DEV/RDISK/DISK34
Volume Group configuration has been restored TO/DEV/RDISK/DISK33
Volume Group configuration has been restored TO/DEV/RDISK/DISK32
Volume Group configuration has been restored TO/DEV/RDISK/DISK31
Volume Group configuration has been restored TO/DEV/RDISK/DISK30
Volume Group configuration has been restored to/dev/rdisk/disk29
Volume Group configuration has been restored TO/DEV/RDISK/DISK28
Volume Group configuration has been restored TO/DEV/RDISK/DISK27
Volume Group configuration has been restored TO/DEV/RDISK/DISK26
Volume Group configuration has been restored TO/DEV/RDISK/DISK25
Creating the Volume Group of version 2.0 with minor number 0x1000.
Adding the Volume group/dev/datavg to/etc/lvmtab_p
Original Volume Group Version was 1.0
New Volume Group Version is 2.0
Volume Group version have been successfully changed to 2.0
Volume Group configuration For/dev/datavg has been saved in/etc/lvmconf/datavg.conf
# #vgchange-A Y/dev/datavg
Activated Volume Group.
Volume Group "/dev/datavg" has been successfully changed.
#vgdisplay/dev/datavg
---Volume groups---
VG Name/dev/datavg
VG Write Access Read/write
VG Status Available
Max LV 511
Cur LV 1
Open LV 1
Max PV 511
Cur PV 20
ACT PV 20
Max PE per PV 65536
VGDA 40
PE Size (Mbytes) 256
Total PE 40580
Alloc PE 40580
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs on use 0
VG Version 2.0
VG Max Size 210000g
VG Max Extents 840000
At this point, the value of Max PV has been increased to 511.
This article from "I Love life" blog, declined reprint!
HPUX 11.31 LVM VG adds one of Max PV methods