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

Chapter 6, Error Messages

Understanding Messages

Note By default, vxconfigd is started at boot time with the -x syslog option. This

redirects vxconfigd console messages to syslog. If you want to retain this

behavior when restarting vxconfigd from the command line, include the -x

syslog argument, as restarting vxconfigd does not preserve the option settings

with which it was previously running. Similarly, any VERITAS Volume Manager

operations that require vxconfigd to be restarted may not retain the behavior that

was previously specified by option settings.

For more information on logging options for vxconfigd, refer to the vxconfigd(1M)

manual page.

Understanding Messages

VxVM is fault-tolerant and resolves most problems without system administrator

intervention. If the configuration daemon (vxconfigd) recognizes the actions that are

necessary, it queues up the transactions that are required. VxVM provides atomic changes

of system configurations; either a transaction completes fully, or the system is left in the

same state as though the transaction was never attempted. If vxconfigd is unable to

recognize and fix system problems, the system administrator needs to handle the task of

problem solving using the diagnostic messages that are returned from the software. The

following sections describe error message numbers and the types of error message that

may be seen, and 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:

◆ 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