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

(For a list of all conditions, see the latest vgversion(1M) manpage.)
When the migration will fail, the vgversion –r output messages should indicate the problem
and possible solutions. For example, if you are migrating a volume group from Version 1.0 to 2.1,
Version 2.1 requires more metadata. Thus, it is possible that there is not enough space in the LUN
for the increase in metadata. In this example, vgversion –r should display the following:
#vgversion -V 2.1 -r -v vg01
Performing "vgchange -a r -l -p -s vg01" to collect data
Activated volume group
Volume group "vg01" has been successfully activated.
The space required for Volume Group version 2.1 metadata on Physical Volume
/dev/disk/disk12 is 8448 KB, but available free space is 1024 KB.
0 free user extents from the end of the Physical Volume /dev/disk/disk12
will be utilized to accommodate the Volume Group version 2.1 metadata.
vgversion: More space for metadata is required. Take one of the following
actions:
1. Free 8 extents more from the end of the Physical Volume
2. Increase the disk size by 7424 KB to avoid using the free user extents
3. Increase the disk size by 7424 KB and use the free user extents
Warning: Volume Group version 2.1 does not support bad block
relocation. The bad block relocation policy of all logical volumes
will be set to NONE.
Deactivating Volume Group "vg01"
Volume group "vg01" has been successfully deactivated.
Review complete. Volume group not modified
Using one of the solutions displayed or using a solution of your own, you must resolve the problem
in order for the migration to be successful. In this case, we could increase the LUN size to allow
for the additional metadata. After you believe you have resolved the problem(s) displayed, you
can try vgversion –r again to determine whether the migration will be successful. Once the
vgversion –r output shows a successful migration, you can execute the actual migration using
vgversion without the –r option.
TIP: Use the –v (Verbose) option along with the –r (Review mode) option to display full details
of the problem. In the above example, if you omit the –v option, the above output would not include
the following details:
The space required for Volume Group version 2.1 metadata on Physical Volume
/dev/disk/disk12 is 8448 KB, but available free space is 1024 KB.
3.3.3.4 Example of Migrating a Volume Group to a Different Version
In this example:
• The target volume is vg01.
• We will be migrating it from version 1.0 to 2.1.
• Assume that the target volume group is currently cluster-unaware but activated.
The process for performing a migration are:
1. Verify the current version of the target volume group:
# vgdisplay vg01 | grep -i version
VG Version 1.0
This shows the current version is 1.0.
2. Review the migration:
# vgversion -r -v -V 2.1 vg01
The space required for Volume Group version 2.1 metadata on
Physical Volume /dev/disk/disk12 is 8448 KB, but available free space
3.3 Common LVM Tasks 51