Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

55Error 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 5.0 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.