Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

a failure related to reading the file /var/vxvm/tempdb/group. This is a temporary
file used to store information that is used when recovering the state of an earlier
vxconfigd. The file is recreated on a reboot, so this error should never survive a
reboot.
Recommended action:
If you can reboot the system, do so. If you do not want to reboot, then use the
following procedure.
To correct the error without rebooting
1
Ensure that no vxvol, vxplex, or vxsd processes are running.
Use ps -e to search for such processes, and use kill to kill any that you find.
You may have to run kill twice to make these processes go away. Killing
utilities in this way may make it difficult to make administrative changes to
some volumes until the system is rebooted.
2
Recreate the temporary database files for all imported disk groups using the
following command:
# vxconfigd -x cleartempdir 2> /dev/console
The vxvol, vxplex, and vxsd commands make use of these tempdb files to
communicate locking information. If the file is cleared, then locking
information can be lost. Without this locking information, two utilities can
end up making incompatible changes to the configuration of a volume.
V-5-1-2524
VxVM vxconfigd ERROR V-5-1:2524 VOL_IO_DAEMON_SET failed: daemon
count must be above N while cluster
Description:
The number of Veritas Volume Manager kernel daemons (vxiod) is less than the
minimum number needed to join a cluster.
Recommended action:
Increase the number of daemons using vxiod.
V-5-1-2630
VxVM vxconfigd WARNING V-5-1-2630 library and vxconfigd disagree on
existence of client number
Description:
99Error messages
Types of messages