Commands Reference, Volume 1

n

The volume group is not automatically activated during system startup.

y

The volume group is automatically activated during system startup.

y

Will turn on the bad-block relocation policy of a volume group.

n

Turns off the bad block relocation policy of a volume group.

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.
6. A big VG only supports Enhanced Concurrent Capable.

Enhanced Concurrent volume groups use Group Services. Group Services ships with HACMP ES and must be configured prior to activating a volume group in this mode.

Use this flag to change a volume group containing Serial DASD or SSA disks into an Enhanced Concurrent Capable volume group.

1. Enhanced Concurrent volume groups use Group Services. Group Services ships with HACMP ES and must be configured prior to activating a volume group in this mode.
2. Only Enhanced Concurrent Capable volume groups are supported when running with a 64 bit kernel. Concurrent Capable volume groups are not supported when running with a 64 bit kernel.

1. The user might be required to execute varyoffvg and then varyonvg on the volume group for LVM to see the size change on the disks.
2. There is no support for re-sizing while the volume group is activated in classic or enhanced concurrent mode.
3. There is no support for re-sizing for the rootvg.

y

Enhances the automatic migration of failed disks by permitting one for one migration of partitions from one failed disk to one spare disk. The smallest disk in the volume group spare pool that is big enough for one to one migration will be used.

Y

Permits the automatic migration of failed disks and allows migration to the entire pool of spare disks, as opposed to a one for one migration of partitions to a spare.

n

Prohibits the automatic migration of a failed disk. This is the default value for a volume group.

r

Removes all disks from the Hotspare pool for the volume group.

1. You cannot use the -L flag if the volume group is varied on in concurrent mode.
2. To change the logical track group size, the volume group is varied off in management mode. This ensures the integrity of the 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.

y

Attempts to automatically synchronize stale partitions.

n

Prohibits automatic synchronization of stale partitions. This is the default for a volume group.

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.

1. If the volume group is created in AIX 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 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.

y

autovaryon the volume group in concurrent mode.

n

autovaryon the volume group in non-concurrent mode.

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