vgversion.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

vgversion(1M) vgversion(1M)

groups version 2.0 and higher may consume more space than on volume groups version 1.0. Please see

the section Extent Sizing for Volume Group Version 2.0 and Higher in lvm(7) for more details.

Note: The major number changes from 64 to 128 when the volume group is upgraded from 1.0 to 2.0 or

higher volume group version.

If the

vgversion command is interrupted before it completes, recovery steps might be required. See

the Recovery section below for details.

Using the Review Mode Option (-r) Prior to Migration

Users can use the review mode option (

-r) of the vgversion command to check whether the migration

operation is possible. For example, the

-r option can be used to check whether all physical volumes have

the additional space required to accommodate the volume group version vg_version_new metadata.

Review mode can be used when the volume group is in activated state. The review option of the

vgver-

sion provides the following details:

• Lists any feature or functionality contained in the existing volume group vg_name which will not be

supported in the migrating volume group version vg_version_new resulting in the failure of migration.

For each such failure, the command displays the corresponding corrective action to be taken to

prepare the volume group for successful migration.

• Whether all the physical volumes in the existing volume group vg_name have sufﬁcient space to hold

the metadata for the migrating volume group version vg_version_new.

For those physical volumes which do not have enough free space to store the metadata of volume

group version vg_version_new, review mode displays the corrective actions to be taken to prepare the

volume group for successful migration (like freeing up required number of extents at the end of the

physical volume or increasing the size of the physical volume by a speciﬁed size).

Migration of Volume Group Version 1.0 to Volume Group Version 2.x

When a volume group is migrated to version 2.2 or higher, the unshare unit is set to the value speciﬁed

by the

-U option or to the default of 1024 KB.

Below are points to consider when migrating from volume group version 1.0 to version 2.x.

• If there are any entries in the bad block directory of any physical volume in the volume group

vg_name,

vgversion fails the migration and reports the physical volume holding entries in the bad

block directory.

• The migration fails if the volume group vg_name has any physical volumes which are conﬁgured as

standby or active spare.

• Volume group versions 2.0 and 2.1 do not support root, boot, swap, or dump. If the volume group ver-

sion of vg_name is 1.0 and is conﬁgured with any of the above, the

vgversion command fails the

migration of such volume groups to version 2.0 or 2.1.

Volume group versions 2.2 and higher do support root, boot, swap, and dump. But the

vgversion

command currently does not support the migration of a volume group version 1.0 with bootable physi-

cal volumes to version 2.2 or higher in the HP-UX 11i v3 March 2010 Update.

• The migration of the volume group version includes moving the conﬁguration details of the volume

group present in the

/etc/lvmtab ﬁle to the /etc/lvmtab_p ﬁle, and converting all the device

special ﬁles present under the /dev/vg_name directory to the format of new volume group version

vg_version_new. This include changing the device ﬁle major and minor number.

• During migration, the size of the volume group may be increased in order to account for all the unused

space on the physical volumes present in the volume group.

• Except where noted above, the volume group version migration process retains all other LVM

conﬁguration/characteristics of the existing volume group vg_name and its logical volumes and physi-

cal volumes. Following a successful volume group version migration,

vgversion retains the order of

the physical volumes in the LVM conﬁguration ﬁles.

Note: Volume group version 2.0 and higher do not support bad block relocation. If any logical volume

belonging to the volume group vg_name has bad block relocation enabled, the

vgversion command will

change the bad block relocation policy of the logical volume to ’NONE’.

Migration of Volume Group Version 2.x to Volume Group Version 2.y

Below is information regarding migration from volume group version 2.x to a version 2.y.

HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3