[Orca-users] Sun Sparc - Replaced disk and Orca fails

[David Devault]

David, 

Yes.  Orca working fine is a temporary situation.

The problem is when I have a disk failure part of the disk replacement
process includes rebooting the system because of the conflicts of stale
information the old disks leave behind.  I'm sure this has something to
do with FC (wwn) because it never happened on a regular SCSI bus.  I
have not tried the -C option for devfsadm and will try that.  I have to
schedule the time since I have a few tests to run and I'm not sure how
the system will react at this point.  I did a quick check to see the
/dev/ device link path names and notice nothing out of the norm.

When a disk fails I feel I should not have to reboot the system.  Orca
works fine the rest of the time.  One of the other things I'm going to
try to do before I reboot is upgrade orca and se on that system.

Thanks, 
David

-----Original Message-----
From: David Michaels [mailto:dragon at raytheon.com] 
Sent: Thursday, August 11, 2005 9:59 AM
To: Cockcroft, Adrian
Cc: David Devault; orca-users at orcaware.com
Subject: Re: [Orca-users] Sun Sparc - Replaced disk and Orca fails

David --

Have you tried "devfsadm -C"?  I've had to use this in rare instances, I

think all of which were related to fiber channel disks, as they do some 
WWN magic that tends to leave junk behind more often than with scsi
disks.

 From the manpages:

     -C    Cleanup mode. Prompts devfsadm to invoke cleanup  rou-
           tines that are not normally invoked to remove dangling
           logical links. If  -c  is  also  used,  devfsadm  only
           cleans up for the listed devices' classes.

One thing I'm confused about:

>When we reboot this problem goes away and orca works fine.
>I'd like to fix this without rebooting.
>

I'm guessing "orca works fine" is a temporary condition?  Seems to me if

you reboot once, and the problem goes away, then there is no residual 
problem to solve.  Or am I missing something?

--Dragon