VERITAS Volume Manager 4.1 Troubleshooting Guide

Error Messages

Understanding Messages

Chapter 6 67

NOTE By default, vxconfigd is started at boot time with the -xsyslog option. This

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

behavior when restarting vxconﬁgd 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 speciﬁed 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 conﬁguration daemon (vxconfigd) recognizes the actions that are

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

system conﬁgurations; 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

ﬁx 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 list

error messages that may be seen along with a more detailed description of the likely cause of

the problem and 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 conﬁguration daemon such as vxconﬁgd, or a

command such as vxassist.

Messages are divided into the following types of severity in decreasing order of impact on the

system:

• PANIC