HP Serviceguard Version A.11.17 on HP-UX 11i v3 Release Notes, February 2007

Serviceguard Version A.11.17 on HP-UX 11i v3 Release Notes
Fixed in This Version
Chapter 1 49
JAGag13268 (SR8606456893): Package using VxVM
fails to start
What was the problem? If cmviewcl failed, a package which used VxVM
disk groups failed to start and reported that a disk group might be
imported on another node, even if this was not the case. The following
was logged in the package log file:
check_dg: Error DG may still be imported on HOST
What was the resolution? The code was modified to check the status of
cmviewcl so it could be retried if it fails.
JAGag13268 (SR8606456893): System can become
unresponsive during a cmquerycl
What was the problem? A system could become unresponsive during a
cmquerycl if there were a large number of logical volumes configured on
the system. For example a system configured with 1400 logical volumes
was unresponsive for 10 minutes while cmquerycl was running. Similar
delay might be experienced with other Serviceguard commands such as
cmgetconf and cmapplyconf.
What was the resolution? The code was modified to open the raw logical
volume device rather than the block logical volume device
JAGag11992 (SR8606455475: boot script takes a long
time to execute
What was the problem? The Serviceguard boot script
/sbin/init.d/cmcluster could take a very long time to execute,
resulting in a long system boot time after a Metrocluster/SRDF package
failover. The following error might appear in /etc/rc.log:
VxVM vxdisk ERROR V-5-1-531 Device c14t12d1:
clearimport failed: Disk write failure
If the Metrocluster/SRDF package was then restarted on the R1 node,
the import of the VxVM data group failed with:
VxVM vxdisk ERROR V-5-1-539 Device c14t12d1:
get_contents failed: Disk device is offline
VxVM vxdg ERROR V-5-1-587 Disk group dgpkgEMC-1: