VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages

Cluster Error Messages

Chapter 3

Cluster Error Messages

This section lists error messages that may occur with VxVM in a cluster environment.

Some of these messages may appear on the console; others are returned by vxclust.

Cannot assign minor minor

• Description: A slave attempted to join, but an existing volume on the slave has the

same minor number as a shared volume on the master.

This message should be accompanied by the following console message:

vxvm:vxconfigd minor number minor disk group group in use

• Action: Before retrying the join, use vxdg reminor (see the vxdg(1M) manual page) to

choose a new minor number range either for the disk group on the master or for the

conﬂicting disk group on the slave. If there are open volumes in the disk group, the

reminor operation will not take effect until the disk group is deported and updated

(either explicitly or by rebooting the system).

Cannot find disk on slave node

• Description: A slave node in a cluster cannot ﬁnd a shared disk. This is accompanied

by the syslog message:

vxvm:vxconfigd cannot find disk disk

• Action: Make sure that the same set of shared disks is online on both nodes. Examine

the disks on both the master and the slave with the command vxdisk list and make

sure that the same set of disks with the shared ﬂag is visible on both nodes. If not,

check the connections to the disks.

Clustering license restricts operation

• Description: An operation requiring a full clustering license was attempted, and such

a license is not available.

• Action: If the error occurs when a disk group is being activated, dissociate all but one

plex from mirrored volumes before activating the disk group. If the error occurs

during a transaction, deactivate the disk group on all nodes except the master.

CVM protocol version out of range

• Description: When a node joins a cluster, it tries to join at the protocol version that is

stored in its volboot ﬁle. If the cluster is running at a different protocol version, the

master rejects the join and sends the current protocol version to the slave. The slave

re-tries with the current version (if that version is supported on the joining node), or

the join fails.

• Action: Make sure that the joining node has a 3.5 release installed that supports the

current protocol version of the cluster.

Disk in use by another cluster

• Description: An attempt was made to import a disk group whose disks are stamped

with the ID of another cluster.

• Action: If the disk group is not imported by another cluster, retry the import using

the -C (clear import) ﬂag.

Disk reserved by other host