From owner-freebsd-isp Sat Dec 6 06:35:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA22013 for isp-outgoing; Sat, 6 Dec 1997 06:35:02 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA21991 for ; Sat, 6 Dec 1997 06:34:53 -0800 (PST) (envelope-from fbsdlist@federation.addy.com) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id JAA06954; Sat, 6 Dec 1997 09:34:45 -0500 (EST) Date: Sat, 6 Dec 1997 09:34:45 -0500 (EST) From: Cliff Addy To: Jeff Lynch cc: "Bryn Wm. Moslow" , freebsd-isp@FreeBSD.ORG, jayk@nwlink.com Subject: Re: Adaptec 2940/Seagate Failures In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 5 Dec 1997, Jeff Lynch wrote: > On Fri, 5 Dec 1997, Bryn Wm. Moslow wrote: > > > breath. The people who DO seem to be having problems are running the 2940 > > under heavy load conditions and having to power cycle servers at horrible > > Possibly a flakey controller? No, we have a half-dozen servers running 2.2.2 and 2940s and they *all* have this problem. These servers were built over a period of a year, so it's not a "bad batch" of controllers, either. The thing that consistently flips them out is a tape write error, although they regularly do it when NO tape i/o is happening. As someone noted earlier, the SCSI code is not very tolerant of errors and is being completely rewritten. The situation can be summarized: - The problem is real, it's not imaginary - It's widespread and common - It's in FBSD - It's being (hopefully) fixed Until then, all we can do is live with it and hope that a future release will let me go back to sleeping easily :) Cliff