VXVM : Resolving duplicate disk/device entries in "vxdisk list" or vxdisksetup

Sometimes, when failed fibre channel disks are replaced in arrays or servers under Veritas Volume Manager control, duplicate entries appear in the vxdisk list output. While Veritas indicates in TechNote 236062 that the ultimate solution is a reconfiguration reboot (or two), recycling the host is often not a viable alternative in mission-critical production environments.

The problem can be seen when running vxdisksetup; the following error message may occur:

  1. vxdisksetup -i c1t5d0

vxdisksetup: c1t5d0: Duplicate DA records encountered for this device.

The same problem can also be seen when running vxdisk list; duplicate entries may occur:

  1. vxdisk list

c0t8d0s2 sliced – – online

c1t2d0s2 sliced c1t2d0s2 rootdg online

c1t3d0s2 sliced c1t3d0s2 ttdg online

c1t5d0s2 sliced c1t5d0s2 – error

c1t5d0s2 sliced c1t5d0s2 – online/error <<– any state is ok.

Veritas Volume Manager (VxVM): Resolving Duplicate disk/device entries in “vxdisk list” or vxdisksetup.

As an example, this is how to resolve the duplicate entry problem, where c1t0d0s2 is the duplicate entry seen via vxdisk list:

Example shown is for c1t0d0s2. Please change c#t#d#s# as per your configuration.

  1. vxdisk list

c1t0d0s2 sliced – – error
c1t0d0s2 sliced – – error
c1t1d0s2 sliced disk01 rootdg online
– – root-disk rootdg removed was:c1t0d0s2

1. Remove c1t0d0s2 entries from vxvm control.

  Run "vxdisk -f rm c1t0d0s2" for all the duplicate entries.
  [Since there is no way to know which one is the valid one,
run it for all. There can also be more than 2 duplicate entries.]
 # vxdisk rm c1t0d0s2
 # vxdisk rm c1t0d0s2 <-- repeat to remove all the entries.

2. Remove the disk c1t0d0s2 using luxadm.

  Remove device c1t0d0s2 using "luxadm remove_device" command.
  [luxadm remove_device cxtydzs2]
 # luxadm remove_device /dev/rdsk/c1t0d0s2
   Pull the disk out as per luxadm instructions.

3. Run command “devfsadm -C”

4. Run command “vxdctl enable”

 [Up to this point, we have removed the dev_t corresponding to the
physical disk. Now we will remove all the stale dev_t's.]
 Please loop as per these instructions:


 [Note that there is one entry less, since we have removed one entry.]
# vxdisk list
c1t0d0s2     sliced    c1t0d0     -         error
c1t1d0s2     sliced    disk01       rootdg       online
-            -         root-disk    rootdg       removed was:c1t0d0s2

5. Again remove *ALL* duplicate c1t0d0s2 entries from vxvm control.

# vxdisk rm c1t0d0s2

6. Run command “luxadm -e offline <device path>” on *ALL THE PATHS*
to the disk [this removes the stale dev_t]

  The test machine had 2 paths to the disk, one through
controller c1, and the other through controller c2.
# luxadm -e offline /dev/dsk/c1t0d0s2
# luxadm -e offline /dev/dsk/c2t0d0s2

If this command returns a “device busy” message, then usually the underlying cause is that one of the slices is configured as the dump device. To determine whether this is the case, run the dumpadm command without any options and check for a cxtydz path in the “Dump device” field.

Use the dumpadm command to ensure that the dump-device is not on the failed disk.

7. Run command “devfsadm -C”

8. Run command “vxdctl enable”

goto LOOP:

[Continue this process until there are no more entries in vxdisk list of corresponding disk c1t0d0s2]

9. You need to use “luxadm insert_device” to replace the disk failed device.

[Once the disk have been replaced, use “vxdctl enable” and “vxdiskadm” option 5 after syncing with the remaining mirror.]


# vxdisk list
DEVICE       TYPE      DISK         GROUP        STATUS
c1t0d0s2     sliced    root-disk    rootdg       online
c1t1d0s2     sliced    disk01       rootdg       online

Now both the O/S device tree and VxVM are in a clean state corresponding to disk c1t0d0s2.



I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

4 Responses

  1. Malya says:

    Hi Gurus,
    I had the same issue, root disk was replaced with unconfiguration and new disk inserted. Then I saw duplicate entries in “VXDISK LIST”, then i followed above steps to replace duplicate entry. after that I have executed below steps, Unfortunately server went down. Can you help me out.

  1. September 18, 2015

    […] Veritas root disk without VxVM, for maintenance Read – Unable to recognize newly-added disks Read – Resolving duplicate disk/device entries in “vxdisk list” or vxdisksetup Read […]

What is in your mind, about this post ? Leave a Reply

  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us