HP-UX System Administrator's Guide: Logical Volume Management (762803-001, March 2014)

Cause
The pvkey of a physical volume can range between 0 to a value equal to one less than the
maximum supported number of physical volumes for a volume group version. If the pvkey of the
physical volume is not in this range for the target Version 2.x volume group, vgversion fails the
migration.
Recommended Action
1. Use lvmadm to determine the maximum supported number of physical volumes for the target
volume group version.
2. Use vgcfgrestore –l –v to check if there is any unused pvkey in the range supported
by the target volume group version.
3. If a valid pvkey is found in this range, add a disk to the volume group and verify that this
physical volume has a pvkey in the supported range. Use pvmove to move all extents from
the physical volume pvname to this new physical volume, so that the physical volume pvname
can be removed from the volume group.
4. If the volume group already contains more than the maximum supported number of physical
volumes for the target volume group version, then the migration cannot be achieved.
If you are not familiar with any of the steps mentioned above, contact your HP support representative
for assistance.
Message Text
Error: The Logical Volume /dev/vgname/lvname has the lv number #,
which is not supported by volume group version 2.x.
Cause
The logical volume number of a logical volume can range between 1 to the maximum supported
number of logical volumes for a volume group version. If the logical volume number of the logical
volume is not in this range for the target Version 2.x volume group, vgversion fails the migration.
Recommended Action
1. Use lvmadm to determine the maximum supported number of logical volumes for the target
volume group version.
2. For each logical volume device file in the /dev/vgname directory, determine the logical
volume number. (Section “Device Number Format” (page 18) describes the format of the
logical volume device file.) Based on the volume group version, decode the bits associated
with the logical volume number and convert this value to decimal notation.
3. Check if there is any unused logical volume number in the range supported by the target
volume group version. If a valid number is found in this range, create a logical volume with
the same properties as that of /dev/vgname/lvname. Copy the entire data from this logical
volume to the one created newly, so that the logical volume /dev/vgname/lvname can be
removed from the volume group.
4. If the volume group already contains more than the maximum supported number of logical
volumes for the target volume group version, then the migration will fail.
If you are not familiar with any of the steps mentioned above, contact your HP support representative
for assistance.
F.16 Log Files and Trace Files: /var/adm/syslog/syslog.log
LVM does not have a dedicated log file or trace file. It logs errors and warnings to
/var/adm/syslog/syslog.log. Below are LVM messages that might appear in this file.
F.16 Log Files and Trace Files: /var/adm/syslog/syslog.log 187