*BSD News Article 6834


Return to BSD News archive

Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!ogicse!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw
From: osynw@gemini.oscs.montana.edu (Nathan Williams)
Newsgroups: comp.unix.bsd
Subject: Re: Problems with SCSI and IDE drives working together.
Keywords: n
Message-ID: <1992Oct19.184954.4391@coe.montana.edu>
Date: 19 Oct 92 18:49:54 GMT
Article-I.D.: coe.1992Oct19.184954.4391
References: <1992Oct19.144609.441@sbcs.sunysb.edu>
Sender: usenet@coe.montana.edu (USENET News System)
Organization: Montana State University
Lines: 60

In article <1992Oct19.144609.441@sbcs.sunysb.edu> csilva@cs.sunysb.edu (Claudio Silva) writes:
>I have 386BSD installed on a 486-25, 20 MB RAM and an IDE 120 MB drive
>for a couple of weeks with no big problems or compatibily issues, I
>was able to run Xfree86 and other software posted on the net without
>any problems.
>
>Now I got a larger SCSI drive (500 MB Fujitsu + AHA 1542B) and
>installed on my system with minor installation headaches. The problem
>now is that the drive seems to work for some functions but on others
>the system just crashes and usually destroy my super-block or leaves
>the whole disk totally inconsistent.
>
>Specifically, I have had the following problems :
>
>       1) COPYING FILES BETWEEN DISKS. 
>		I can copy files between disks as long as I only
>		copy one file at a time. If I try things like
>		"cp <old-dir>/* <new-dir" the system just crashes.
>		I can copy single HUGE files with no problem. To
>		solve this problem I created a shell script that
>		call "cp" with the files one at a time.
>
>       2) REMOVING FILES FROM NEW DISK.
>		If I try "rm *" in the new disk, the system crashes
>		and certainly will destroy most of the data in the 
>		new disk, sometimes the "rm <file>" works, sometimes
>		it doesn't.
>
>I don't have any idea of what maybe causing these problems and I will
>be very happy if someone could help solve them. Any pointers to
>possible solutions would be very welcome.
>

I had similar results to this when I added a second SCSI drive to
my system.  With one drive, my system was as stable as a rock with
all of the patches I had put together installed, but when I added
the second drive, any heavy disk activity paniced my system.  

Since that time, I have installed Julian's new SCSI drivers, and
though I can still panic the system, it doesn't happen with near
the frequency as before (Now it takes running a make;make clean in
my kernel directory, which I suspect has nothing to do with the
SCSI drivers.)

Since installing Julian's new drivers, my machine is much more stable,
and just for grins and giggles, I download the mt(1) command from
gatekeeper.dec.com to work with my tape drive, and it worked *flawlessly*.
I can now do multi-volume dumps, so I am one happy 386BSD'er.  

Now that I finally got all the bugs worked out of my system, I hope
to get time to update the Bug List to sync with Terry Lambert's 
patch kit, and add a couple new patches.


Nate

-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.