Veritas Volume Manager 4.1 Troubleshooting Guide (HP-UX 11i v3, February 2007)

Understanding Messages
52 VERITAS Volume Manager Troubleshooting Guide
◆ 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.
The unique message number consists of an alpha-numeric string that begins with the
letter “V”. For example, in the message number, V-5-1-3141, “V” indicates that this is a
VERITAS product error message, the first numeric field (5) encodes the product (in this
case, VxVM), the second field (1) represents information about the product component,
and the third field (3141) is the message index. The text of the error message follows the
message number.