I am still looking for similar situations. One modification to the technote routine is, if the SF version is more recent than 5.0 MP3, the reboot can be replaced with "vxddladm -c assign names"
On Thu, Aug 18, 2011 at 1:02 AM, Lupin Deterd <[email protected]> wrote: > On Wed, Aug 17, 2011 at 10:13 PM, William Havey <[email protected]> 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 <[email protected]> > 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 > emcpower17c > >> emcpower18s2 auto - - error > emcpower18c > >> emcpower19s2 auto - - error > emcpower19c > >> emcpower20s2 auto - - error > emcpower20c > >> emcpower21s2 auto - - error > emcpower21c > >> emcpower22s2 auto - - error > emcpower22c > >> > >> > >> Would deleting the disk.info file, help? > >> > >> TIA, > >> > >> lupin > >> > >> On Wed, Aug 17, 2011 at 1:46 AM, William Havey <[email protected]> > wrote: > >> > Lupin > >> > vxconfigd reads a file /etc/vx/disk.info in some versions of VM. See > if > >> > this > >> > ascii text file exists, then if it does, edit out the lines in the > file > >> > which concern the "ghost" disks and reset vxconfigd again. > >> > Bill > >> > > >> > > >> > On Tue, Aug 16, 2011 at 7:19 AM, Lupin Deterd <[email protected]> > >> > wrote: > >> >> > >> >> 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 > >> > > >> > > >> > > >> > -- > >> > William (Bill) Havey > >> > Symantec Certified HA Professional > >> > 917 515-3385 > >> > > >> > > > > > > > > > -- > > William (Bill) Havey > > Symantec Certified HA Professional > > 917 515-3385 > > > > > -- William (Bill) Havey Symantec Certified HA Professional 917 515-3385
_______________________________________________ Veritas-vx maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
