Managing Serviceguard 12th Edition, March 2006

Configuring Packages and Their Services
Creating the Package Control Script
Chapter 6292
CAUTION Although Serviceguard uses the -C option within the package control
script framework, this option should not normally be used from the
command line. The “Troubleshooting” section 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
This command takes over ownership of all the disks in disk group dg_01,
even though the disk currently has a different host ID written on it. The
command writes the current node’s host ID on all disks in disk group
dg_01 and sets the noautoimport flag for the disks. This flag prevents a
disk group from being automatically re-imported by a node following a
reboot. If a node in the cluster fails, the host ID is still written on each
disk in the disk group. However, if the node is part of a Serviceguard
cluster then on reboot the host ID will be cleared by the owning node
from all disks which have the noautoimport flag set, even if the disk
group is not under Serviceguard control. This allows all cluster nodes,
which have access to the disk group, to be able to import the disks as
part of cluster operation.
The control script also uses the vxvol startall command to start up
the logical volumes in each disk group that is imported.
Optimizing for Large Numbers of Storage Units
A set of four variables is provided to allow performance improvement
when employing a large number of filesystems or storage groups. For
more detail, see the comments in the control script template. The three
variables are summarized below
• CONCURRENT_VGCHANGE_OPERATIONS—defines a number of parallel
LVM volume group activations during package startup as well and
deactivations during package shutdown.
• CONCURRENT_FSCK_OPERATIONS—defines a number of parallel fsck
operations that will be carried out at package startup.