HP-UX 11i v3 - LVM Volume Group Version Migration (September 2010)

17
vgversion status messages
While using the vgversion command you may see status messages similar to the following:
A Version 2.x Volume Group with the minor number 0x1000 already exists
The minor number is already used by a Version 2.x volume group. The vgversion command
selects the first available minor number. While converting a Version 1.0 volume group to a
2.x volume group, vgversion tries to retain the volume group minor number as is.
Adding the Volume Group /dev/vg01 to /etc/lvmtab_p
After successfully applying the configuration corresponding to the new volume group to the physical
volumes, vgversion added the volume group entry to /etc/lvmtab_p file.
Applying the configuration to all Physical Volumes from
"/etc/lvmconf/vgversion_vg01/vg01_2.1.conf"
The vgversion command called vgcfgrestore to apply the configuration corresponding to the
final volume group version to the physical volumes.
Error: Cannot change the version of a cluster aware Volume Group.
The vgversion command failed the migration operation because the volume group is configured
as cluster aware. When a volume group is configured as cluster aware and deactivated on the
local node, it might be active on another node. In these cases, continuing with migration causes
undesirable consequences.
Error: Could not find any free minor number for volume group Version 2.1
The vgversion command did not find a free minor number to create the volume group group file
because all the minor numbers are used by the existing Version 2.x volume groups. This can occur
when the maximum supported number of volume groups was already created.
Error: Failed to apply the new configuration on all Physical Volumes of the
Volume Group.
The vgversion command calls vgcfgrestore to apply the new configuration on the physical
volumes. While applying the configuration if any of the physical volumes becomes unavailable,
vgversion tries to revert back to the initial volume group version metadata.
Error: Failed to update the /etc/lvmtab_p with the Volume Group “/dev/vg01”
The addition of volume group entries to the /etc/lvmtab_p file failed. The physical volumes
belonging to the volume group are vulnerable to data loss. HP recommends you run the restore
script after fixing the reason for the error. When a Version 1.0 volume group is converted to 2.x,
the vgversion command removes the volume group entry from /etc/lvmtab and adds it to
/etc/lvmtab_p.
Error: Kernel does not support version change operation.
The vgversion command does not support migration to the requested volume group.
Error: The Logical Volume "/dev/vg01/lvol512" has the lv number 512, which is
not supported by volume group Version 2.0
The lv number of a logical volume is more than 511; vgversion failed the migration. To continue
with the migration, delete those logical volumes and recreate them.
Error: The number of Logical Volumes in the Volume Group "/dev/vg01" is 520.
But Volume Group Version 2.0 supports up to 511 Logical Volumes.
The minor number of the logical volume is greater than what is supported by the requested final
volume group version; vgversion failed the migration.