From owner-freebsd-questions  Tue Jun 17 13:38:37 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA05865
          for questions-outgoing; Tue, 17 Jun 1997 13:38:37 -0700 (PDT)
Received: from shop95 ([207.137.172.43])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA05860;
          Tue, 17 Jun 1997 13:38:32 -0700 (PDT)
Message-ID: <33A6F664.5F8D582F@ccsales.com>
Date: Tue, 17 Jun 1997 13:41:08 -0700
From: "Randy A. Katz" <randyk@ccsales.com>
Reply-To: randyk@ccsales.com
Organization: CCSales, Inc.
X-Mailer: Mozilla 4.0 [en] (Win95; I)
MIME-Version: 1.0
To: Cliff Addy <fbsdlist@federation.addy.com>
CC: questions@FreeBSD.ORG
Subject: Re: SCSI bus timeouts
X-Priority: 3 (Normal)
References: <Pine.BSF.3.95q.970617160007.17823A-100000@federation.addy.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Guess what?

I setup a very minimal machine on my network (P75,16MB RAM, Ample SCSI-2
Hard Drive Space) with a DAT drive and Freebsd 2.1.0...rock solid.

...backs up some urgently important files never would want to take them
off tape anyway types (too slow) every morning at arount 1:39 am through
a temporary mount to the other machines.

...It also dumps to tape the other machines at around 2:30 am.

Works like a charm, is fast, stable, inexpensive (not cheap, good
motherboard, Adaptec 2940, nice old hard drives but good).

Hope this helps though it's NOT a soLuTion.

Randy Katz


Cliff Addy wrote:
> 
> What has happened to my lovely little FreeBSD systems?  They used to be so
> stable, so rock-solid reliable.  Now they don't even stay up a day
> anymore.
> 
> What happened?  I "upgraded" them to 2.2, since then my life has been
> hell.  I thought 2.2.2 was going to fix the problem with lockups during
> tape backups.  But the newest system, running the latest code off the ftp
> site, just died with that same "SCSI bus timed out" error message.
> 
> This was not a "heavily loaded" system, it was brand new and doing
> *nothing* but a backup.  On our systems, about 35% of our backups to tape
> lock up the machine with the bus timeouts.
> 
> Does anyone have an idea on how to fix this?  We're running the same
> hardware that stayed up for weeks at a time under 2.1.5, Cyrix 6x86, 64MB,
> Adaptec 2940UW, Seagate HDD and DAT.