Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

56 Error messages
Understanding messages
Messages are divided into the following types of severity in decreasing order of impact on
the system:
PANIC 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
FATAL ERROR 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
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.
WARNING 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
NOTICE A notice message indicates that an error has occurred that should be
monitored. Shutting down the system is unnecessary, although you
may need to take action to remedy the fault at a later date. The
following is an example of such a message:
VxVM vxio NOTICE V-5-0-252 read error on object subdisk of mirror
plex in volume volume (start offset, length length) corrected.
INFO An informational message does not indicate an error, and requires no
action.