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

provide a list of the more common errors, a detailed description of the likely cause
of the problem together with suggestions for any actions that can be taken.
Messages have the following generic format:
product component severity message_number message_text
For Veritas Volume Manager, the product is set to VxVM. The component can be
the name of a kernel module or driver such as vxdmp, a configuration daemon
such as vxconfigd, or a command such as vxassist.
Messages are divided into the following types of severity in decreasing order of
impact on the system:
A panic is a severe event as it halts a system during its normal
operation. A panic message from the kernel module or from
a device driver indicates a hardware problem or software
inconsistency so severe that the system cannot continue. The
operating system may also provide a dump of the CPU register
contents and a stack trace to aid in identifying the cause of
the panic. The following is an example of such a message:
VxVM vxio PANIC V-5-0-239 Object association
depth overflow
PANIC
A fatal error message from a configuration daemon, such as
vxconfigd, indicates a severe problem with the operation
of VxVM that prevents it from running. The following is an
example of such a message:
VxVM vxconfigd FATAL ERROR V-5-0-591 Disk group
bootdg: Inconsistency -- Not loaded into kernel
FATAL ERROR
An error message from a command indicates that the
requested operation cannot be performed correctly. The
following is an example of such a message:
VxVM vxassist ERROR V-5-1-5150 Insufficient
number of active snapshot mirrors in
snapshot_volume .
ERROR
A warning message from the kernel indicates that a
non-critical operation has failed, possibly because some
resource is not available or the operation is not possible. The
following is an example of such a message:
VxVM vxio WARNING V-5-0-55 Cannot find device
number for boot_path
WARNING
Error messages
Types of messages
64