Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

79Error messages
Understanding messages
V-5-1-809
VxVM vxplex ERROR V-5-1-809 Plex plex in volume volume is locked by
another utility.
■ Description: The vxplex command fails because a previous operation to attach a
plex did not complete. The
vxprint command should show that one or both of the
temporary and persistent utility fields (TUTIL0 and PUTIL0) of the volume and one
of its plexes are set.
■ Action: If the vxtask list command does not show a task running for the volume,
use the
vxmend command to clear the TUTIL0 and PUTIL0 fields for the volume
and all its components for which these fields are set:
# vxmend -g diskgroup clear all volume plex ...
V-5-1-923
VxVM vxplex ERROR V-5-1-923 Record volume is in disk group
diskgroup1 plex is in group diskgroup2.
■ Description: An attempt was made to snap back a plex from a different disk group.
■ Action: Move the snapshot volume into the same disk group as the original volume.
V-5-1-1171
VxVM vxconfigd ERROR V-5-1-1171 Version number of kernel does not
match vxconfigd
■ Description: The release of vxconfigd does not match the release of the Veritas
Volume Manager 5.0 kernel drivers. This should happen only as a result of
upgrading VxVM, and then running vxconfigd without a reboot.
■ Action: Reboot the system. If that does not cure the problem, re-add the VxVM
packages.
V-5-1-1186
VxVM vxconfigd ERROR V-5-1-1186 Volume volume for mount point /usr
not found in bootdg disk group
■ Description: The system is configured to boot with /usr mounted on a volume, but
the volume associated with /usr is not listed in the configuration of the boot disk
group. There are two possible causes of this error:
■ Case 1: The /etc/fstab file was erroneously updated to indicate the device
for the /usr file system is a volume, but the volume named is not in the boot
disk group. This should happen only as a result of direct manipulation by the
administrator.