|
|
HP-UX Reference Volume 2 of 5 > vvgchange(1M) |
|
NAMEvgchange — set LVM volume group availability SYNOPSISActivate volume group/usr/sbin/vgchange -a availability [-l] [-p] [-q quorum] [-s] [-P resync_daemon_count] [vg_name...] Assign to high availability cluster and mark volume group sharable/usr/sbin/vgchange -c cluster -S sharable vg_name RemarksMC/ServiceGuard cluster operations require the installation of the optional MC/ServiceGuard software, which is not included in the standard HP-UX operating system. Lock Manager cluster operations require the installation MC/LockManager software which is not included with the standard HP-UX operating system. Mirrored disk operations require the installation of the optional HP MirrorDisk/UX software, which is not included in the standard HP-UX operating system. DESCRIPTIONThe vgchange command with the -a option activates or deactivates one or more volume groups. The vgchange command with the -c option controls the membership of one or more volume groups in a high availability cluster. The vgchange command with the -c and -S options control the membership of a volume group and mark it sharable. The vgchange command without the -P resync_daemon_count option (default) will spawn one nomwcsyncd process for each NOMWC/NONE volume group being activated. This may create a lot of nomwcsyncd processes running concurrently when it activates a large number of NOMWC/NONE volume groups and overload. The -P resync_daemon_count option provides a way to control the number of concurrent nomwcsyncd processes. The count is an advisory number and a different count might be chosen internally if load balance or other reason is needed. When specified, there are up to resync_daemon_count + 1 nomwcsyncd processes; one of them is the controlling processing to spawn others. -P 0 will use the system default (currently defined to be 4). vg_name must be defined as a volume group in the file /etc/lvmtab. If vg_name is omitted, all volume groups defined in /etc/lvmtab are affected. High Availability Cluster OverviewVolume groups can be defined on disk volumes that are connected to two or more systems in a high availability cluster. This situation has a high potential for data corruption unless special software is used to coordinate shared access to the same volume group by all systems. This coordination is provided by MC/ServiceGuard or MC/LockManager. A volume group can be marked as part of a MC/ServiceGuard cluster. When such a group is activated in exclusive mode, it can be accessed for exclusive read-write activity by only one of the systems at a time; the other systems can have read-only access to the data. A volume group can be marked as a part of an MC/LockManager cluster. In this case, the volume group can be marked as sharable, and may be activated in shared mode for read-write access by all the nodes in the cluster. Shared read-write access by multiple cluster nodes is coordinated by MC/LockManager's distributed lock manager (DLM). Options and Argumentsvgchange recognizes the following options and arguments:
Mirrored Disk ActivationWhen the optional HP MirrorDisk/UX software is running and a volume group is activated, LVM performs the necessary mirror consistency recovery for each logical volume in the volume group based on the state of Mirror Write Cache and Mirror Consistency Recovery (see the Consistency Recovery section of lvdisplay(1M)). In a non-shared environment, LVM supports MWC, NOMWC and the NONE recovery. But in shared environment, LVM only supports NOMWC and the NONE recovery.
Next, mirror synchronization refreshes stale mirror copies by copying data from a nonstale copy. If the -s option is specified on the command line, mirror synchronization does not occur. However, for those logical volumes that have Mirror Write Cache turned off, mirror synchronization is done independently of whether the -s option appears on the command line. General ActivationIf vgchange cannot access a physical volume, it lists the volume's status as missing. If too many physical volumes in the volume group are missing, vgchange reports that the group does not have a quorum and cannot be activated. The lack of a quorum can be overridden with the -q n option. EXTERNAL INFLUENCESEnvironment VariablesLANG determines the language in which messages are displayed. If LANG is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLESActivate volume group /dev/vg03: vgchange -a y /dev/vg03 Deactivate volume group /dev/vg03: vgchange -a n /dev/vg03 Activate volume group /dev/vg03 without synchronizing extents that are not current on logical volumes that have Mirror Write Cache turned on: vgchange -a y -s /dev/vg03 Exclusive ActivationSet up volume group /dev/vg03 for use in a high availability cluster: vgchange -a n /dev/vg03 # Deactivate volume group vgchange -c y /dev/vg03 # Enable volume group for HA cluster vgchange -c y -S y /dev/vg03 # Enable volume group for HA cluster and mark as sharable vgchange -a e /dev/vg03 # Activate volume group in exclusive mode vgchange -a s /dev/vg03 # Activate volume group in shared mode Activate all volume groups; activate those that are marked for membership in a high availability cluster in exclusive mode: vgchange -a y Activate all volumes that are marked for membership in a high availability cluster in exclusive mode: vgchange -a e WARNINGSOrdinary OperationIn ordinary operation (i.e., without the optional high availability software), it is possible to activate a volume group for read-write access from more than one physically connected system, leading to a high potential for data corruption. Therefore, if access is desired from more than one system to a single volume group, it is important that only one system activate the volume group for read-write access; the other systems can use read-only access. There is no problem if all systems activate the volume group for read-only access. Furthermore, volume group information is only read from the disks during volume group activation. Dynamic changes to the volume group such as the following are not propagated to other systems sharing the volume group:
Because of these limitations, when sharing volume groups between systems it is recommended that logical volumes be accessed only by one system at a time. If logical volumes need to be accessed simultaneously, the logical volumes should not be mirrored and should not have bad-block relocation turned on, or all systems should use read-only access to the logical volumes. SEE ALSOmount(1M), vgcreate(1M), vgextend(1M), vgreduce(1M), vgdisplay(1M). If MC/ServiceGuard is installed: cmcheckconf(1M), cmquerycl(1M), and Managing MC/ServiceGuard. |
|