From owner-freebsd-current  Mon Nov 13 23:00:41 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id XAA02877
          for current-outgoing; Mon, 13 Nov 1995 23:00:41 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA02871
          for <current@freebsd.org>; Mon, 13 Nov 1995 23:00:37 -0800
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id XAA27864; Mon, 13 Nov 1995 23:00:36 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id XAA00132; Mon, 13 Nov 1995 23:00:35 -0800
Message-Id: <199511140700.XAA00132@corbin.Root.COM>
To: Heikki Suonsivu <hsu@cs.hut.fi>
cc: current@freebsd.org
Subject: Re: ISP state their FreeBSD concerns 
In-reply-to: Your message of "Tue, 14 Nov 95 08:48:42 +0200."
             <199511140648.IAA28625@shadows.cs.hut.fi> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 13 Nov 1995 23:00:34 -0800
Sender: owner-current@freebsd.org
Precedence: bulk

>David Greenman writes:
> > >The troubling disks for us seem to be seagate hawks, but I have also had
> > >problems with an ibm 0662 (but it could be seagates in the same bus).  I
> > >have tried a 2G barracuda and 4G hawk for news spool, both with same
> > >results, disk gets confused and scsi driver returns I/O errors for all
> > >accesses or the system panics.
> > 
> >    We've been having similar problems with Seagate Hawks on wcarchive. I plan
> > to switch them out for 4GB Quantum Grand Prixs in the near term.
>
>Have you discussed about this with seagate?  With sparcs they seem to work
>just fine.

   No, I haven't. I think the Hawks have firmware bug(s) that only show up
after days of heavy disk I/O and/or when interacting with drives from other
manufacturers. I have very little patience for this this kind of thing which
is why I have no plans to mess around with Seagate tech support. Of course
it's also possible that there is a problem with the Adaptec 2940 sequencer
code that's in FreeBSD, but I'm beginning to seriously doubt that.

-DG