Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

83Error messages
Understanding messages
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 5.0 kernel daemons (vxiod)
is less than the minimum number needed to join a cluster.
■ 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: This warning may safely be ignored.
■ Action: None required.
V-5-1-2824
VxVM vxconfigd ERROR V-5-1-2824 Configuration daemon error 242
■ Description: A node failed to join a cluster, or a cluster join is taking too long. If the
join fails, the node retries the join automatically.
■ Action: No action is necessary if the join is slow or a retry eventually succeeds.
V-5-1-2829
VxVM vxdg ERROR V-5-1-2829 diskgroup: Disk group version doesn’t
support feature; see the vxdg upgrade command
■ Description: The version of the specified disk group does not support disk group
move, split or join operations.
■ Action: Use the vxdg upgrade diskgroup command to update the disk group
version.