Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

65Error messages
Understanding messages
V-5-0-386
VxVM vxio WARNING V-5-0-386 subdisk subdisk failed in plex plex in
volume volume
■ Description: The kernel has detected a subdisk failure, which may mean that the
underlying disk is failing.
■ Action: Check for obvious problems with the disk (such as a disconnected cable). If
hot-relocation is enabled and the disk is failing, recovery from subdisk failure is
handled automatically.
V-5-1-90
VxVM vxconfigd ERROR V-5-1-90 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.
V-5-1-91
VxVM vxconfigd WARNING V-5-1-91 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
V-5-1-92
VxVM vxconfigd WARNING V-5-1-92 Cannot exec /usr/bin/rm to remove
directory: reason
■ Description: The given directory could not be removed because the /usr/bin/rm
utility could not be executed by vxconfigd. This is not a serious error. The only
side effect of a directory not being removed is that the directory and its contents
continue to use space in the root file system. However, this does imply that the /
usr file system is not mounted, or on some systems, that the rm utility is missing or
is not in its usual location. This may be a serious problem for the general running of
your system.
■ Action: If the /usr file system is not mounted, you need to determine how to get it
mounted. If the rm utility is missing, or is not in the /usr/bin directory, restore it.