For the disk that doesn't exist anymore I see:

c3::50001fe15005e90a,11        unavailable  connected    configured   unusable

c3::50001fe15005e90c,11        unavailable  connected    configured   unusable

So only two paths of 8 are still hanging there.


-----Original Message-----
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 

Long time ago means a few months ago but during this uptime.


-----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 

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         TAOS            http://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 


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 

Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu

Reply via email to