Managing Serviceguard 12th Edition, March 2006

Troubleshooting Your Cluster
Solving Problems
Chapter 8 385
2. b - vxfen
3. v w - cvm
4. f - cfs
Any form of the mount command (for example, mount -o cluster,
dbed_chkptmount, or sfrac_chkptmount) other than cfsmount or
cfsumount in a HP Serviceguard Storage Management Suite
environment with CFS should be done with caution. These non-cfs
commands could cause conflicts with subsequent command operations on
the file system or Serviceguard packages. Use of these other forms of
mount will not create an appropriate multi-node package which means
that the cluster packages are not aware of the file system changes.
Also check the syslog file for information.
Problems with VxVM Disk Groups
This section describes some approaches to solving problems that may
occur with VxVM disk groups in a cluster environment. For most
problems, it is helpful to use the vxdg list command to display the disk
groups currently imported on a specific node. Also, you should consult
the package control script log files for messages associated with
importing and deporting disk groups on particular nodes.
Force Import and Deport After Node Failure
After certain failures, packages configured with VxVM disk groups will
fail to start, and the following error will be seen in the package log file:
vxdg: Error dg_01 may still be imported on ftsys9
ERROR: Function check_dg failed
This can happen if a package is running on a node which then fails before
the package control script can deport the disk group. In these cases, the
host name of the node that had failed is still written on the disk group
header.
When the package starts up on another node in the cluster, a series of
messages is printed in the package log file, as in the following example
(the hostname of the failed system is ftsys9, and the disk group is dg_01):
check_dg: Error dg_01 may still be imported on ftsys9
To correct this situation, logon to ftsys9 and