Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
How Control Scripts Manage VxVM Disk Groups
Chapter 6 323
How Control Scripts Manage VxVM Disk
Groups
VxVM disk groups (other than those managed by CVM) are outside the
control of the Serviceguard cluster. The package control script uses
standard VxVM commands to import and deport these disk groups. (For
details on importing and deporting disk groups, refer to the discussion of
the import and deport options in the vxdg man page.)
The control script imports disk groups using the vxdg command with the
-tfC options. The -t option specifies that the disk is imported with the
noautoimport flag, which means that the disk will not be automatically
re-imported at boot time. Since disk groups included in the package
control script are only imported by Serviceguard packages, they should
not be auto-imported.
The -f option allows the disk group to be imported even if one or more
disks (a mirror, for example) is not currently available. The -C option
clears any existing host ID that might be written on the disk from a prior
activation by another node in the cluster. If the disk had been in use on
another node which has gone down with a TOC, then its host ID may still
be written on the disk, and this needs to be cleared so the new node’s ID
can be written to the disk. Note that the disk groups are not imported
clearing the host ID if the host ID is set and matches a node that is not in
a failed state. This is to prevent accidental importation of a disk group on
multiple nodes which could result in data corruption.
CAUTION Although Serviceguard uses the -C option within the package control
script framework, this option should not normally be used from the
command line. Chapter 8, “Troubleshooting Your Cluster,” on page 405,
shows some situations where you might need to use -C from the
command line.
The following example shows the command with the same options that
are used by the control script:
# vxdg -tfC import dg_01