Managing Serviceguard 13th Edition, February 2007

Configuring Packages and Their Services
Creating the Package Control Script
Chapter 6 279
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.
• CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS—defines a number of
parallel mount operations during package startup and unmount
operations during package shutdown.
You can use the -s option with FSCK_OPT and FS_UMOUNT_OPT
parameters for environments that use a large number of filesystems. The
-s option allows mount/umounts and fscks to be done in parallel. (With
the standard 11iv1 (11.11) HP-UX, you need to install patches to get this
option.)
Package Control Script Template File
The following is an excerpt from a sample package control script
template file. The file contains separate sections for activation of VxVM
and LVM storage groups.