VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)
Error Messages
vxconfigd Error Messages
Chapter 3
68
Evaluate the error messages to determine the root cause of the problem. Make
changes suggested by the errors and then try rerunning the command.
vxvm:vxconfigd: ERROR: Failed to store commit status list into kernel:
reason
vxvm:vxconfigd: ERROR: GET_VOLINFO ioctl failed:
reason
vxvm:vxconfigd: ERROR: Get of current rootdg failed:
reason
• Description: These internal errors should not occur unless there is a bug in VxVM.
• Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: Memory allocation failure
• Description: This implies that there is insufficient memory to start VxVM.
• Action: This error should not normally occur, unless your system has very small
amounts of memory. Adding swap space will probably not help because this error is
most likely to occur early in the boot sequence, before swap areas have been added.
vxvm:vxconfigd: ERROR:
mode
: Unrecognized operating mode
• Description: An invalid string was specified as an argument to the -m option. Valid
strings are: enable, disable, and boot.
• Action: Supply a correct option argument.
vxvm:vxconfigd: ERROR: Mount point
path
: volume not in rootdg disk group
• Description: The volume device listed in the /etc/fstab file for the given
mount-point directory (normally /usr) is listed as in a disk group other than rootdg.
This error should not occur if the standard Veritas Volume Manager procedures are
used for encapsulating the disk containing the /usr file system.
• Action: Boot VxVM from a network or CD-ROM mounted root file system. Then,
start up VxVM using fixmountroot on a valid mirror disk of the root file system.
After starting VxVM, mount the root file system volume and edit the /etc/fstab
file. Change the file to use a direct partition for the file system. There should be a
comment in the /etc/fstab file that indicates which partition to use.
vxvm:vxconfigd: ERROR: No convergence between root disk group and disk
list
Disks in one version of rootdg: device type=
device_type
info=
devinfo
...
Disks in alternate version of rootdg: device type=
device_type
info=
devinfo
...
• Description: This message can appear when vxconfigd is not running in
autoconfigure mode (see the vxconfigd (1M) manual page) and after several retries it
cannot resolve the set of disks belonging to the root disk group. The algorithm for
non-autoconfigure disks scans disks listed in the /etc/vx/volboot file and then
examines the disks to find a database copy for the rootdg disk group. It next reads
the database copy to find the list of disk access records for disks contained in the
group. These disks are then examined to ensure that they contain the same database
copy. The algorithm expects to gain convergence on the set of disks and on the
database copies that they contain. If a loop is entered and convergence cannot be
reached, this message is displayed and the root disk group importation fails.
• Action: Reorganize the physical locations of the devices attached to the system to try
and break the deadlock. If this does not succeed, contact Customer Support.
vxvm:vxconfigd: ERROR: Open of directory
directory
failed:
reason