Re: [Veritas-vx] removing devices
Hello, For the disk that doesn't exist anymore I see: c3::50001fe15005e90a,11unavailable connectedconfigured unusable c3::50001fe15005e90c,11unavailable connectedconfigured unusable So only two paths of 8 are still hanging there. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: lunes, 23 de abril de 2007 23:22 To: Jarkko Airaksinen; Veritas-vx@mailman.eng.auburn.edu Subject: RE: [Veritas-vx] removing devices what kind of output do you get with? # cfgadm -o show_FCP_dev -al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen Sent: Thursday, April 12, 2007 4:12 AM To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices Yes, in a way it's present as I don't disconnect the whole SAN :). I just do the normal device removal process (umount fs, remove volume from the disk group etc) and finally unpresent it from the SAN. What makes this odd is that sometimes the removal works just fine. On a slow day when there's not much action in the server I've tried disabling all paths for the other of the two adapters with cfgadm but the paths stay regardless. Long time ago means a few months ago but during this uptime. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: miércoles, 11 de abril de 2007 20:03 To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices I suppose this is because the device paths don't get cleaned even with devfsadm -C. Close. 'devfsadm -C' removes device files if the *device* is gone. However in your case the device is still present (but no longer connected to storage). How a device is handled depends on your storage driver(s). Some can handle removal without a reboot, some can't. Best would be if you could go in with cfgadm and disable the storage. However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. I think the Solaris device does still exist in the kernel and storage driver. Does long time ago mean before or after the last reboot? How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. You have to ask the device driver to do it, and there's no global way of asking. 'cfgadm disable ...' would be the usual way for a recent Sun-supplied san driver. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx __ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended only for the use of the addressee named above.If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any diffusion, distribution or duplication of this communication is strictly forbidden, and please notify us immediately by return to the original message at the address above eliminating it afterwards. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] removing devices
okay do this.. # cfgadm -o unusable_FCP_dev -c unconfigure c3::50001fe15005e90a and # cfgadm -o unusable_FCP_dev -c unconfigure c3::50001fe15005e90c if it doesn't remove it use the force option: cfgadm -f -o unusable_..rest of the command... after they are gone I usually use the devfsadm -C to clean up anything and then after that you should be able to use the vxdisk rm DEVICE where the DEVICE is from the vxdisk list -Original Message- From: Jarkko Airaksinen [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 5:23 AM To: Hart, Tony; Veritas-vx@mailman.eng.auburn.edu Subject: RE: [Veritas-vx] removing devices Hello, For the disk that doesn't exist anymore I see: c3::50001fe15005e90a,11unavailable connectedconfigured unusable c3::50001fe15005e90c,11unavailable connectedconfigured unusable So only two paths of 8 are still hanging there. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: lunes, 23 de abril de 2007 23:22 To: Jarkko Airaksinen; Veritas-vx@mailman.eng.auburn.edu Subject: RE: [Veritas-vx] removing devices what kind of output do you get with? # cfgadm -o show_FCP_dev -al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen Sent: Thursday, April 12, 2007 4:12 AM To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices Yes, in a way it's present as I don't disconnect the whole SAN :). I just do the normal device removal process (umount fs, remove volume from the disk group etc) and finally unpresent it from the SAN. What makes this odd is that sometimes the removal works just fine. On a slow day when there's not much action in the server I've tried disabling all paths for the other of the two adapters with cfgadm but the paths stay regardless. Long time ago means a few months ago but during this uptime. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: miércoles, 11 de abril de 2007 20:03 To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices I suppose this is because the device paths don't get cleaned even with devfsadm -C. Close. 'devfsadm -C' removes device files if the *device* is gone. However in your case the device is still present (but no longer connected to storage). How a device is handled depends on your storage driver(s). Some can handle removal without a reboot, some can't. Best would be if you could go in with cfgadm and disable the storage. However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. I think the Solaris device does still exist in the kernel and storage driver. Does long time ago mean before or after the last reboot? How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. You have to ask the device driver to do it, and there's no global way of asking. 'cfgadm disable ...' would be the usual way for a recent Sun-supplied san driver. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx __ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended only for the use of the addressee named above.If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any diffusion, distribution or duplication of this communication is strictly forbidden, and please notify us immediately by return to the original message at the address above eliminating it afterwards. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman
Re: [Veritas-vx] removing devices
what kind of output do you get with? # cfgadm -o show_FCP_dev -al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen Sent: Thursday, April 12, 2007 4:12 AM To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices Yes, in a way it's present as I don't disconnect the whole SAN :). I just do the normal device removal process (umount fs, remove volume from the disk group etc) and finally unpresent it from the SAN. What makes this odd is that sometimes the removal works just fine. On a slow day when there's not much action in the server I've tried disabling all paths for the other of the two adapters with cfgadm but the paths stay regardless. Long time ago means a few months ago but during this uptime. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: miércoles, 11 de abril de 2007 20:03 To: Veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] removing devices I suppose this is because the device paths don't get cleaned even with devfsadm -C. Close. 'devfsadm -C' removes device files if the *device* is gone. However in your case the device is still present (but no longer connected to storage). How a device is handled depends on your storage driver(s). Some can handle removal without a reboot, some can't. Best would be if you could go in with cfgadm and disable the storage. However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. I think the Solaris device does still exist in the kernel and storage driver. Does long time ago mean before or after the last reboot? How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. You have to ask the device driver to do it, and there's no global way of asking. 'cfgadm disable ...' would be the usual way for a recent Sun-supplied san driver. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx __ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended only for the use of the addressee named above.If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any diffusion, distribution or duplication of this communication is strictly forbidden, and please notify us immediately by return to the original message at the address above eliminating it afterwards. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] removing devices
Hello, # /etc/vx/diag.d/vxdmpinq /dev/rdsk/c3t50001FE15005E90Ad6s2 ioctl failed: I/O error VxVM vxdmpinq ERROR V-5-1-8853 /etc/vx/diag.d/vxdmpinq for /dev/rdsk/c3t50001FE15005E90Ad6s2. ioctl failed., evpd 0 page code 0. I/O error Usually all paths get removed automatically as they should. However at times only some (or none) of the paths disappear when I remove the disk. I'll play with the driver a bit and see if I can disable them manually. -j- -Original Message- From: Myers, Mike [mailto:[EMAIL PROTECTED] Sent: miércoles, 11 de abril de 2007 18:56 To: Jarkko Airaksinen; [EMAIL PROTECTED] Subject: RE: [Veritas-vx] removing devices So if you run /etc/vx/diag.d/vxdmpinq /dev/rdsk/c3t50001FE15005E90Ad6s2 what do you get? It certainly looks like the disks are still visible... Cheers, - Mike Myers, mike.myers at nwdc.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen Sent: Wednesday, April 11, 2007 9:21 AM To: [EMAIL PROTECTED] Subject: [Veritas-vx] removing devices Hello, I've removed some disks from the server but they keep on coming back for example after vxdisk scandisks': # vxdisk list DEVICE TYPEDISK GROUPSTATUS EVA8_1 auto:cdsdiskpt_dwhdg146_01 pt_dwhdg146 online nohotuse EVA8_3 auto:cdsdiskpt_dwhdg146_02 pt_dwhdg146 online nohotuse EVA8_4 auto:cdsdiskpt_dwhdg250_01 pt_dwhdg250 online nohotuse EVA8_5 auto:cdsdiskpt_dwhdg250_02 pt_dwhdg250 online nohotuse EVA8_7 auto:cdsdiskpt_dwhdg146_03 pt_dwhdg146 online nohotuse EVA8_8 auto--error EVA8_9 auto:cdsdiskpt_dwhdg146_04 pt_dwhdg146 online nohotuse EVA8_10 auto--error EVA8_11 auto:cdsdiskpt_dwhdg250_04 pt_dwhdg250 online nohotuse EVA8_12 auto--error EVA8_13 auto:cdsdiskpt_dwhdg250_06 pt_dwhdg250 online nohotuse EVA8_14 auto:cdsdiskpt_dwhdg250_05 pt_dwhdg250 online nohotuse EVA8_15 auto--error c0t0d0s2 auto:sliced rootdg01 rootdg online nohotuse c1t0d0s2 auto:sliced rootdg02 rootdg online nohotuse I suppose this is because the device paths don't get cleaned even with devfsadm -C. For example these are the paths to EVA8_8: # ls -la /dev/dsk/*d6s2 lrwxrwxrwx 1 root root 69 Feb 26 16:31 c3t50001FE15005E90Ad6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 17:39 c3t50001FE15005E90Bd6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 17:39 c3t50001FE15005E90Cd6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 16:31 c3t50001FE15005E90Dd6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 16:31 c5t50001FE15005E908d6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 16:31 c5t50001FE15005E909d6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Mar 1 13:47 c5t50001FE15005E90Ed6s2 - /../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 21:57 c5t50001FE15005E90Fd6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. -j- ___ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended
Re: [Veritas-vx] removing devices
Yes, in a way it's present as I don't disconnect the whole SAN :). I just do the normal device removal process (umount fs, remove volume from the disk group etc) and finally unpresent it from the SAN. What makes this odd is that sometimes the removal works just fine. On a slow day when there's not much action in the server I've tried disabling all paths for the other of the two adapters with cfgadm but the paths stay regardless. Long time ago means a few months ago but during this uptime. -j- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: miércoles, 11 de abril de 2007 20:03 To: [EMAIL PROTECTED] Subject: Re: [Veritas-vx] removing devices I suppose this is because the device paths don't get cleaned even with devfsadm -C. Close. 'devfsadm -C' removes device files if the *device* is gone. However in your case the device is still present (but no longer connected to storage). How a device is handled depends on your storage driver(s). Some can handle removal without a reboot, some can't. Best would be if you could go in with cfgadm and disable the storage. However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. I think the Solaris device does still exist in the kernel and storage driver. Does long time ago mean before or after the last reboot? How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. You have to ask the device driver to do it, and there's no global way of asking. 'cfgadm disable ...' would be the usual way for a recent Sun-supplied san driver. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-vx maillist - [EMAIL PROTECTED] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx __ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended only for the use of the addressee named above.If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any diffusion, distribution or duplication of this communication is strictly forbidden, and please notify us immediately by return to the original message at the address above eliminating it afterwards. ___ Veritas-vx maillist - [EMAIL PROTECTED] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
Re: [Veritas-vx] removing devices
So if you run /etc/vx/diag.d/vxdmpinq /dev/rdsk/c3t50001FE15005E90Ad6s2 what do you get? It certainly looks like the disks are still visible... Cheers, - Mike Myers, mike.myers at nwdc.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarkko Airaksinen Sent: Wednesday, April 11, 2007 9:21 AM To: Veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] removing devices Hello, I've removed some disks from the server but they keep on coming back for example after vxdisk scandisks': # vxdisk list DEVICE TYPEDISK GROUPSTATUS EVA8_1 auto:cdsdiskpt_dwhdg146_01 pt_dwhdg146 online nohotuse EVA8_3 auto:cdsdiskpt_dwhdg146_02 pt_dwhdg146 online nohotuse EVA8_4 auto:cdsdiskpt_dwhdg250_01 pt_dwhdg250 online nohotuse EVA8_5 auto:cdsdiskpt_dwhdg250_02 pt_dwhdg250 online nohotuse EVA8_7 auto:cdsdiskpt_dwhdg146_03 pt_dwhdg146 online nohotuse EVA8_8 auto--error EVA8_9 auto:cdsdiskpt_dwhdg146_04 pt_dwhdg146 online nohotuse EVA8_10 auto--error EVA8_11 auto:cdsdiskpt_dwhdg250_04 pt_dwhdg250 online nohotuse EVA8_12 auto--error EVA8_13 auto:cdsdiskpt_dwhdg250_06 pt_dwhdg250 online nohotuse EVA8_14 auto:cdsdiskpt_dwhdg250_05 pt_dwhdg250 online nohotuse EVA8_15 auto--error c0t0d0s2 auto:sliced rootdg01 rootdg online nohotuse c1t0d0s2 auto:sliced rootdg02 rootdg online nohotuse I suppose this is because the device paths don't get cleaned even with devfsadm -C. For example these are the paths to EVA8_8: # ls -la /dev/dsk/*d6s2 lrwxrwxrwx 1 root root 69 Feb 26 16:31 c3t50001FE15005E90Ad6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 17:39 c3t50001FE15005E90Bd6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 17:39 c3t50001FE15005E90Cd6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 16:31 c3t50001FE15005E90Dd6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 16:31 c5t50001FE15005E908d6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 16:31 c5t50001FE15005E909d6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Mar 1 13:47 c5t50001FE15005E90Ed6s2 - ./../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c lrwxrwxrwx 1 root root 69 Feb 26 21:57 c5t50001FE15005E90Fd6s2 - ../../devices/[EMAIL PROTECTED],2000/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],6:c However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. -j- ___ La información incluida en el presente correo electrónico es CONFIDENCIAL, siendo para el uso exclusivo del/os destinatario/s arriba mencionado/s. Si usted recibe y lee este correo electrónico y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida cualquier divulgación, distribución, uso o reproducción del mismo, y le rogamos que nos lo notifique inmediatamente respondiendo al mensaje original a la dirección arriba mencionada y eliminando el mensaje a continuación. The information contained in this e-mail is CONFIDENTIAL and is intended only for the use of the addressee named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any diffusion, distribution or duplication of this communication is strictly forbidden, and please notify us immediately by return to the original message at the address above eliminating it afterwards. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
Re: [Veritas-vx] removing devices
I suppose this is because the device paths don't get cleaned even with devfsadm -C. Close. 'devfsadm -C' removes device files if the *device* is gone. However in your case the device is still present (but no longer connected to storage). How a device is handled depends on your storage driver(s). Some can handle removal without a reboot, some can't. Best would be if you could go in with cfgadm and disable the storage. However the devices definitely don't exist anymore. I've deleted the disk from the SAN long time ago. I think the Solaris device does still exist in the kernel and storage driver. Does long time ago mean before or after the last reboot? How would you remove the dangling device entries (without rebooting) if devfsadm -C doesn't clear them? The server has Sol8 + VxVM5.0. You have to ask the device driver to do it, and there's no global way of asking. 'cfgadm disable ...' would be the usual way for a recent Sun-supplied san driver. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
