Notes:

1. The -B flag cannot be used if there are any stale physical partitions or there are any open logical volumes in the volume group.
2. Once the volume group is converted, it cannot be imported into AIX 4.3.1 or lower versions.
3. The -B flag cannot be used if the volume group is varied on in concurrent mode.
4. There must be enough free partitions available on each physical volume for the VGDA expansion for this operation to be successful.
5. Since the VGDA resides on the edge of the disk and it requires contiguous space for expansion, the free partitions are required on the edge of the disk. If those partitions are allocated for user usage, they will be migrated to other free partitions on the same disk. The rest of the physical partitions will be renumbered to reflect the loss of the partitions for VGDA usage. This will change the mappings of the logical to physical partitions in all the PVs of this VG. If you have saved the mappings of the LVs for a potential recovery operation, you should generate the maps again after the completion of the conversion operation. Also, if the backup of the VG is taken with the map option and you plan to restore using those maps, the restore operation may fail since the partition number may no longer exist (due to reduction). It is recommended that backup is taken before the conversion, and right after the conversion if the map option is utilized. Since the VGDA space has been increased substantially, every VGDA update operation (creating an LV, changing an LV, adding a PV, and so forth) may have a considerably longer duration.

Note: You can transform a non-concurrent volume group into a Concurrent Capable volume group. However, you can not transform a Concurrent Capable volume group into a non-concurrent capable volume group.

n

The volume group stays active until it loses all of its physical volumes.

y

The volume group is automatically varied off after losing its quorum of physical volumes.

Note: Run the bosboot or savebase command after the chvg -Q n or chvg -Q y command to update the boot image.

If factor is not supplied, it is set to the lowest value such that the number of physical partitions of the largest disk in volume group is less than factor x 1016.

If factor is specified, the maximum number of physical partitions per physical volume for this volume group changes to factor x 1016.

Notes:

1. If the volume group is created in AIX 3.2/4.1.2 in violation of 1016 physical partitions per physical volume limit, this flag can be used to convert the volume group to a supported state. This will ensure proper stale/fresh marking of partitions.
2. factor cannot be changed if there are any stale physical partitions in the volume group.
3. Once volume group is converted, it cannot be imported into AIX 4.3.0 or lower versions.
4. This flag cannot be used if the volume group is varied on in concurrent mode.
5. The maximum number of physical volumes that can be included in this volume group will be reduced to (MAXPVS/factor).
6. Change of the volume group may require the modification of the LVM meta data. In this situation the volume group will be varied off in management mode to ensure the integrity of the Volume group, needing the closure of all open logical volumes in this volume group. Since logical volumes in rootvg cannot be closed, rootvg cannot be converted if it needs modification of the meta-data as part of the chvg -t operation.

Note: Before using the -u flag, make sure that the volume group is not being used by another LVM command.

y

autovaryon the volume group in concurrent mode.

n

autovaryon the volume group in non-concurrent mode.

Note: If the volume group is not created Concurrent Capable, this command has no effect on the volume group.

In order for this auto-varyon into concurrency of the volume group to take effect, you must enter the following line into the /etc/inittab file:

rc_clvmv:2:wait:/usr/sbin/clvm_cfg 2>&1

Attention: This entry must be added after the entry used to initiate srcmstr.