[2967] in linux-scsi channel archive
Re: BusLogic problems...
daemon@ATHENA.MIT.EDU (Steffen Grunewald)
Thu Dec 18 05:44:41 1997
From: Steffen Grunewald <steffen@gfz-potsdam.de>
To: goemon@sasami.anime.net (Dan Hollis)
Date: Thu, 18 Dec 1997 11:34:02 +0100 (MET)
Cc: steffen@gfz-potsdam.de, root@olupot.astra.net, lnz@dandelion.com,
rstagg@csc.com, linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.96.971218015211.25285A-100000@sasami.anime.net> from "Dan Hollis" at Dec 18, 97 01:56:04 am
"Dan Hollis writes"
|>
|> On Thu, 18 Dec 1997, Steffen Grunewald wrote:
|> > "Dan Hollis writes"
|> > |> Might as well include the Seagate ST43400N in the blacklist as being
|> > |> unable to handle synchronous transfers.
|> > Huh?
|> >
|> > esp0: Target 2 now Synchronous at 4.0 mb/s max transmit rate
|> > sd2 at esp0 target 2 lun 0
|> > sd2: <Seagate ST43400N cyl 2732 alt 2 hd 21 sec 99>
|> >
|> > That's from an old Sparc2 running SunOS 4.1.3 ...
|> >
|> > Didn't find any message of falling back to async mode, thus it should
|> > work in sync mode, too...
|>
|> If you run them hard (e.g. raid0 striped array of several of them), they
|> lock up hard, as in they require a power cycle to recover. Probably that
|> Sparc2 can't run that seagate hard enough to crash it.
|>
|> But our news server can. (4 x ST43400N striped with raid0).
Does that lockup depend on the transmit rate ?
I had been running several Elite3's from a Sparc5 and a Sparc10, too.
Never had lockups.
Perhaps limiting the tx rate would help here ?
Steffen
