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:
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
Messages are divided into the following types of severity in decreasing order of impact on the system:
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:
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.