Re: [Veritas-vx] Ghost VXVM Devices
This seems to be the right track but we may not have gone far enough. By this I mean I went to sort.symantec.con and searched on the error code V-5-1-8645. I got two hits. I selected the second, www.symantec.com/docs/TECH61541 because it referenced a tech note. The note is about Netbackup but, ignoring that, the end of the note states to do this ** *Resolution: *Move the contents of the /etc/vx/disk.info, /etc/vx/array.info and /etc/vx/ jbod.info directories to an alternate location and reboot: # mv /etc/vx/disk.info /root/etc_vx_disk.info.OLD # mv /etc/vx/array.info /root/etc_vx_array.info.OLD # mv /etc/vx/jbod.info /root/etc_vx_jbod.info.OLD # reboot If a reboot is possible the above listed files will be re-created. If reboot is not possible, I'd use vxconfigd -k -m enable On Wed, Aug 17, 2011 at 1:43 AM, Lupin Deterd lupindet...@gmail.com wrote: Hi Bill, After doing what you've suggested(edited the file), I encountered this error during the vxconfigd -k. root@sv3# vxconfigd -k VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed10s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed6s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed3s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed8s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed12s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed7s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed9s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed11s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed8s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed2s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed1s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed11s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed12s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c5t5006016839A0222Ed8s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed6s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed10s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower3c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower8c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower21c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower19c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower15c by NR list: No such device or address And the list afterwards, those disks comes up again. vxdisk -e -o alldgs list DEVICE TYPE DISK GROUPSTATUS OS_NATIVE_NAME EMC_CLARiiON0_0 auto - -error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - -error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - -error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - -error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - -error c2t5006016930603960d0s2 EMC_CLARiiON1_0 auto - -error c5t5006016139A0222Ed0s2 c6t0d0s2 auto - -online c6t0d0s2 c6t1d0s2 auto - -online c6t1d0s2 c6t2d0s2 auto - -online c6t2d0s2 emcpower9s2 auto - -erroremcpower9c emcpower10s2 auto - -erroremcpower10c emcpower11s2 auto - -erroremcpower11c emcpower12s2 auto - -erroremcpower12c emcpower13s2 auto - -erroremcpower13c emcpower14s2 auto - -erroremcpower14c emcpower15s2 auto - -erroremcpower15c emcpower17s2 auto - -erroremcpower17c emcpower18s2 auto - -erroremcpower18c emcpower19s2 auto -
Re: [Veritas-vx] Ghost VXVM Devices
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: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of veritas-vx-requ...@mailman.eng.auburn.edu Sent: Tuesday, August 16, 2011 10:30 PM To: veritas-vx@mailman.eng.auburn.edu Subject: Veritas-vx Digest, Vol 61, Issue 3 Send Veritas-vx mailing list submissions to veritas-vx@mailman.eng.auburn.edu 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 veritas-vx-requ...@mailman.eng.auburn.edu You can reach the person managing the list at veritas-vx-ow...@mailman.eng.auburn.edu 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 lupindet...@gmail.com Subject: [Veritas-vx] Ghost VXVM Devices To: veritas-vx@mailman.eng.auburn.edu 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 TYPEDISK GROUPSTATUS 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 - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx End of Veritas-vx Digest, Vol 61, Issue 3 * ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] Ghost VXVM Devices
On Wed, Aug 17, 2011 at 10:13 PM, William Havey bbha...@gmail.com wrote: This seems to be the right track but we may not have gone far enough. By this I mean I went to sort.symantec.con and searched on the error code V-5-1-8645. I got two hits. I selected the second, www.symantec.com/docs/TECH61541 because it referenced a tech note. The note is about Netbackup but, ignoring that, the end of the note states to do this Resolution: Move the contents of the /etc/vx/disk.info, /etc/vx/array.info and /etc/vx/jbod.info directories to an alternate location and reboot: # mv /etc/vx/disk.info /root/etc_vx_disk.info.OLD # mv /etc/vx/array.info /root/etc_vx_array.info.OLD # mv /etc/vx/jbod.info /root/etc_vx_jbod.info.OLD # reboot If a reboot is possible the above listed files will be re-created. If reboot is not possible, I'd use vxconfigd -k -m enable On Wed, Aug 17, 2011 at 1:43 AM, Lupin Deterd lupindet...@gmail.com wrote: Thanks Bill, I might try this. Hi Bill, After doing what you've suggested(edited the file), I encountered this error during the vxconfigd -k. root@sv3# vxconfigd -k VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed10s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed6s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed3s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed8s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed12s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed7s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed9s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed11s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed8s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed2s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed1s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016039A0222Ed11s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed12s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c5t5006016839A0222Ed8s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed6s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/c2t5006016939A0222Ed10s2 by NR list: I/O error VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower3c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower8c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower21c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower19c by NR list: No such device or address VxVM vxconfigd ERROR V-5-1-8645 Error in claiming /dev/rdsk/emcpower15c by NR list: No such device or address And the list afterwards, those disks comes up again. vxdisk -e -o alldgs list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME EMC_CLARiiON0_0 auto - - error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - - error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - - error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - - error c2t5006016930603960d0s2 EMC_CLARiiON0_0 auto - - error c2t5006016930603960d0s2 EMC_CLARiiON1_0 auto - - error c5t5006016139A0222Ed0s2 c6t0d0s2 auto - - online c6t0d0s2 c6t1d0s2 auto - - online c6t1d0s2 c6t2d0s2 auto - - online c6t2d0s2 emcpower9s2 auto - - error emcpower9c emcpower10s2 auto - - error emcpower10c emcpower11s2 auto - - error emcpower11c emcpower12s2 auto - - error emcpower12c emcpower13s2 auto - - error emcpower13c emcpower14s2 auto - - error emcpower14c emcpower15s2 auto - - error emcpower15c emcpower17s2 auto - - error
