VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

vxconfigd Warning Messages
58 VERITAS Volume Manager Troubleshooting Guide
(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. Ifthe root file system is defined on avolume, thenstart and mount the root
volume. Ifthe root filesystem is not definedon a volume, mount theroot file system
directly. Edit the /etc/fstab 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 another
host. If you turn off drives, run the following command after booting:
# vxdg flush rootdg
Thisupdates timestamps onthe importedversion of rootdg,which shouldmake the
correct version appear to be the more recently accessed. If this does not correct the
problem, contact Customer Support.
vxconfigd Warning Messages
A warning message from the configuration daemon, vxconfigd, indicates a problem
that may affect the operation of VxVM. Action should be taken to correct the problem as
soon as possible.
vxvm:vxconfigd: WARNING: Bad request number: client number, portal
[REQUEST|DIAG], size number
◆ Description: This diagnostic message indicates that a utility sent an invalid request to
vxconfigd.
◆ Action: If you are developing a new utility, this error indicates a bug in your code.
Otherwise, it indicates a bug in VxVM. Contact Customer Support.
vxvm:vxconfigd: WARNING: Cannot change disk group record in kernel:
reason
◆ Description: This internal error should not occur unless there is a bug in VxVM.
◆ Action: Contact Customer Support.
vxvm:vxconfigd: WARNING: Cannot create device device_path: reason
◆ Description: vxconfigd cannot create a device node either under /dev/vx/dsk or
under /dev/vx/rdsk. This should happen only if the root file system has run out
of inodes.
◆ Action: Remove some unwanted files from the root file system. Then, regenerate the
device node using the command:
# vxdctl enable