Logical Volume Manager (LVM) is automatically starting a volume group on all systems in the cluster when the volume group should be controlled by VERITAS Cluster Server (VCS.)
Article ID: 100028173
Updated On:
Resolution
LVM should be configured to not automatically start volume groups that will be controlled by VCS. The parameter is system wide. When the change is made, all volume groups not under VCS control must be explicitly started.
From VERITAS Cluster Server 1.3.1 Installation Guide HP-UX - page 29*:
Modifying lvmrc File
You must modify the file /etc/lvmrc to prevent LVM from automatically starting all volume groups when the system reboots. Additionally, you can specify which of the
non-shared bus volume groups to activate. Note that you must modify the /etc/lvmrc file on each system in the cluster.
You can use the vgdisplay command (for example, vgdisplay /dev/vg*) to list volume groups currently imported on the system. Then select which volume groups should be started.
Edit /etc/lvmrc:
Change
"AUTO_VG_ACTIVATE=1" to "AUTO_VG_ACTIVATE=0".2. Change the function custom_vg_activation() by editing lines to start only those volume groups that are not on the shared bus, as in the example below, where vg00 is the root logical volume and vg01 is a non-shared bus volume group:
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
return 0
}
Change them to read:
custom_vg_activation()
{
/sbin/vgchange -a y -s
parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
return 0
}
Save and close the file.
* This procedure is the same for all version of VCS and has been tested with LVM on HP-UX 11. For HP-UX versions other then 11 consult the product documentation.
Issue/Introduction
