scu on 4.0f (sometimes fails?)

From: Adam Bentley (ccx009@coventry.ac.uk)
Date: Fri Oct 11 2002 - 06:21:26 EDT


Hi,
  just a query. I was doing a lot of hammering on a newly built advfs
domain last night (a RAID 5 partition behind an HSZ70) and unfortunately i
had a domain panic. Not to worry as I figured I could start over and do it
again as the data could be easily placed there again... I know I probably
 should get the boxes patched up to the latest kit (they are upgraded 4.0d
boxes with PK3 for 4.0d... anyway...arrgh I know, no 4.0f kits at all....)

Anyway, aside from the domain panic this raised an interesting issue.
Having seen the volume concerned go off-line, I figured it was just a case
of rebuilding the domain and fileset info....

For some reason however 'scu scan edt' refused to see the raid parition.
It saw everything else BUT my raidset. I checked the controllers and as
far as they were concerned the disks where fine and available... in the
end I rebooted the system and lo-and-behold the scu command now reported
the raid parition as being visible again.

Does scu have 'issues' and if so, is there any other way to get a bus scan
to pick up the disks on my hsz without rebooting?

thanks.
-- _
                                                   /-\dam
-------------------------------------------------------------------------
FLESH: Adam Bentley, Systems/Networking/Usenet, Coventry University. UK
INET : A.Bentley@coventry.ac.uk
-------------------------------------------------------------------------
                        #include <std/disclaimer.h>
-------------------------------------------------------------------------



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:56 EDT