VERITAS Volume Manager 3.1 Reference Guide

Chapter 2 61
Error Messages
Volume Manager Configuration Daemon Error Messages
is not in the rootdg disk group. This should happen only as a
result of direct manipulation by the administrator.
• The system somehow has a duplicate rootdg disk group, one of
which contains the /usr file system volume and one of which does
not (or uses a different volume name), and vxconfigd somehow
chose the wrong rootdg. Since vxconfigd chooses the more
recently accessed version of rootdg, this error can happen if the
system clock was updated incorrectly at some point (causing the
apparent access order of the two disk groups to be reversed). This
can also happen if some disk group was deported and renamed to
rootdg with locks given to this host.
• Action
In case 1, boot the system on a CD-ROM or networking-mounted root
file system. If the root file system is defined on a volume, then start
and mount the root volume using the procedures defined in the
“Recovery” chapter of the Administrator’s Guide. If the root file
system is not defined on a volume, then just mount the root file
system directly. Edit the /etc/vfstab file to correct the entry for the
/usr file system.
In case 2, either boot with all drives in the offending version of
rootdg turned off, or import and rename[see vxdg(1M)] the offending
rootdg disk group from anotherhost. In the case of turning off drives,
run the following command after booting:
vxdg flush rootdg
This will update time stamps on the imported version of rootdg,
which should make the correct version appear to be the more recently
accessed. If this does not correct the problem, then contact Customer
Support.
cannot open /dev/vx/config
vxvm:vxconfigd: ERROR: cannot open /dev/vx/config:
reason
• Description
The /dev/vx/config device could not be opened. vxconfigd uses
this device to communicate with the Volume Manager kernel drivers.
The reason string indicates the reason for the open failure. The most
likely reason is Device is already open. This reason indicates that
some process (most likely vxconfigd) already has /dev/vx/config