Just do "vxdisk rm <name>" on each of the ghost devices and check. VxVM sometimes keeps records of disks it has seen in the past
With regards Hari -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, August 16, 2011 10:30 PM To: [email protected] Subject: Veritas-vx Digest, Vol 61, Issue 3 Send Veritas-vx mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Veritas-vx digest..." Today's Topics: 1. Ghost VXVM Devices (Lupin Deterd) ---------------------------------------------------------------------- Message: 1 Date: Tue, 16 Aug 2011 19:19:13 +0800 From: Lupin Deterd <[email protected]> Subject: [Veritas-vx] Ghost VXVM Devices To: [email protected] Message-ID: <cal0mbks-azjigw7_shw_v5jyuetkagiqaebszdr0d1keqhc...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi All, I need some help tips on this, basically I don't know the exact history of this server but I just destroy the last DG and remove the disk that is part of that DG on the VXVM control. I did: # vxvol -g dg_name stopall # vxdg destroy dg_name # vxdisk rm disk_name # unbind the LUN(EMC) # clear the dead paths # devfsadm -C # vxdctl enable # vxconfigd -k after that I got this this additional Devices(EMC_*): which not there before when I run the same command. # vxdisk list DEVICE TYPE DISK GROUP STATUS EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON0_0 auto - - error EMC_CLARiiON1_0 auto - - error c6t0d0s2 auto:none - - online invalid c6t1d0s2 auto:none - - online invalid c6t2d0s2 auto:none - - online invalid # vxdisk list EMC_CLARiiON1_0 Device: EMC_CLARiiON1_0 devicetag: EMC_CLARiiON1_0 type: auto flags: online error private autoconfig errno: Device path not valid Multipathing information: numpaths: 4 c5t5006016139A0222Ed0s2 state=disabled c5t5006016839A0222Ed0s2 state=disabled c2t5006016039A0222Ed0s2 state=disabled c2t5006016939A0222Ed0s2 state=disabled My question is where did this coming from? And why it's not there until I reset the vxconfigd? TIA, lupin ------------------------------ _______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx End of Veritas-vx Digest, Vol 61, Issue 3 ***************************************** _______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
