Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

61Error messages
Understanding messages
V-5-0-148
VxVM vxdmp NOTICE V-5-0-148 enabled path path_device_number belonging
to dmpnode dmpnode_device_number
■ Description: A path has been marked enabled in the DMP database. This
path is controlled by the DMP node indicated by the specified device
number. This happens if a previously disabled path has been repaired, the
user has reconfigured the DMP database using the
vxdctl(1M) command, or
the DMP database has been reconfigured automatically.
■ Action: None.
V-5-0-164
VxVM vxio WARNING V-5-0-164 Failed to join cluster name , aborting
■ Description: A node failed to join a cluster. This may be caused by the node
being unable to see all the shared disks. Other error messages may provide
more information about the disks that cannot be found.
■ Action: Use the vxdisk -s list command on the master node to see what
disks should be visible to the slave node. Then check that the operating
system and VxVM on the failed node can also see these disks. If the
operating system cannot see the disks, check the cabling and hardware
configuration of the node. If only VxVM cannot see the disks, use the
vxdctl
enable command to make it scan again for the disks. When the disks are
visible to VxVM on the node, retry the join.
V-5-0-166
VxVM vxio WARNING V-5-0-166 Failed to log the detach of the DRL
volume volume
■ Description: An attempt failed to write a kernel log entry indicating the loss
of a DRL volume. The attempted write to the log failed either because the
kernel log is full, or because of a write error to the drive. The volume
becomes detached.
■ Action: Messages about log failures are usually fatal, unless the problem is
transient. However, the kernel log is sufficiently redundant that such errors
are unlikely to occur.
If the problem is not transient (that is, the drive cannot be fixed and
brought back online without data loss), recreate the disk group from scratch
and restore all of its volumes from backups. Even if the problem is
transient, reboot the system after correcting the problem.
If error messages are seen from the disk driver, it is likely that the last copy
of the log failed due to a disk error. Replace the failed drive in the disk