VERITAS Volume Manager 4.1 Troubleshooting Guide

Error Messages
Understanding Messages
Chapter 6 107
V-5-1-5162
VxVM vxplex ERROR V-5-1-5162 Plexes do not belong to the same snapshot
volume.
• Description: An attempt was made to snap back plexes that belong to different snapshot
volumes.
• Action: Specify the plexes in separate invocations of vxplexsnapback.
V-5-1-5929
VxVM vxconfigd NOTICE V-5-1-5929 Unable to resolve duplicate diskid.
• Description: When VxVM detects disks with duplicate disk IDs (unique internal
identifiers), VxVM attempts to select the appropriate disk (using logic that is specific to an
array). If a disk can not be selected, VxVM does not import any of the duplicated disks
into a disk group. In the rare case when VxVM cannot make the choice, you must choose
which duplicate disk to use.
NOTE In releases prior to 3.5, VxVM selected the first disk that it found if the
selection process failed. FromVxVM 3.5 onward, the default behavior is to
avoid the selection of the wrong disk as this could lead to data corruption.
Arrays with mirroring capability in hardware are particularly susceptible
to such data corruption.
• Action: User intervention is required in the following cases:
— Case 1: When DMP is disabled to an array that has multiple paths, then each path to
the array is claimed as a unique disk.
If DMP is suppressed, VxVM does not know which path to select as the true path.You
must choose which path to use. Decide which path to exclude, and then either edit the
file /etc/vx/vxvm.exclude,or, if vxconfigd is running, select item 1 (suppress all paths
through a controller from VxVM’s view) or item 2 (suppress a path from VxVM’s view)
from vxdiskadm option 17 (Prevent multipathing/Suppress devices from VxVM’s
view).
The following example shows a vxvm.exclude file with paths c8t0d0, c8t0d1, and
c8t0d2 excluded from VxVM:
exclude_all 0
paths
c8t0d0 /0/4/0/0.8.0.108.0.0.0