vxdisk list shows removed disks

[Shawn Miller_2]

I removed some disks and may not have done it in the best way. All the file systems were unmounted and all volumes with this diskgroup were stopped. I then did a vxdg destroy of that diskgroup. Then I removed access to those disks on the san. I did a rmsf to remove the device files. You can not see the disks if you do a ioscan. However vxdisk list will show errors for all of those disks. vxprint -hrt will not show any disks. You can not remove the disks with vxdiskadm since it will say they do not exists. Which is correct. The OS does not see those disks. How do I get the output in vxdisk list not to show those disks.

[Kent Ostby]

I think you can clean this up if you go into vxdiskadm and select option 3 "remove a disk for replacement".

[Ralph Grothe]

Hi Shawn,

I guess you have run vxdiskunsetup on the raw device?

This should release the disk from VxVM.

Then the disk should show up with Error state when you run "vxdisk -o alldgs list".

After that it usually is required to release the disk from the OS.

On Solaris (that's where we run VxVM) I'd issue a "devfsadm -c disk" after having disconnected the disk.

Finally I think you must signal VxVM of the departure of the disk.

Usually I would run a "vxdctl enable",
after which the vxdisk list from above shouldn't list the disk anymore.

Be careful when you're doing this on a rootdg disk that is your boot disk.
It requires a dual reconfiguration boot by VxVM to reconvert the disk into the former slices (at least under Solaris)

[Shawn Miller_2]

vxdiskunsetup will return an error:
Device cXtXdX: online failed: Device
path not valid.

Using vxdiskadm and option 3 does not work since vxdiskadm does not show the disks I am trying to cleanup. vxdiskadm and vxprint commands show more what I would expect. It is basically the vxdisk list command that shows disks that the OS no longer sees.

This is HP_UX 11.23 and Veritas 3.5.

My goal is to cleanup the vxdisk list output.

[Michael Roberts_3]

Try
vxdisks scandisks
to update VxVM's cached info on disks.

[Shawn Miller_2]

Thanks for the suggestions. The way I resolved the issue was with --
vxdisk rm cXtXdX.