From owner-freebsd-current Wed Apr 28 14:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B67B114C86 for ; Wed, 28 Apr 1999 14:54:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA26755; Wed, 28 Apr 1999 14:54:07 -0700 Date: Wed, 28 Apr 1999 14:54:07 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Christopher T. Johnson" Cc: freebsd-current@freebsd.org Subject: Re: Further on tape & CAM problems In-Reply-To: <199904282144.RAA38142@neunacht.netgsi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > I'm sorry- I missed the front end of this. I've had pretty good luck with > > getting the 8200 to work. What f/w level are you at for the 8200? > > > > -matt > > Matt, it isn't a tape drive problem. Nor is it directly and exabyte problem. > It is a problem where an error from the tape drive is not being handled > well at the kernel interface. It is as if the kernel is sending a block > to the drive, the drive is giving or holding and error state, the kernel > sees the drive drop the block but instead of reporting an error back to > user land, it reports "ok". User land then proceeds to dump tons of > bytes down the pipe with out really writing it to tape. > Yes, but I'd like to know what error condition is inducing the driver and/or CAM issues. Has anyone tried a CAMDEBUG kernel and camcontrol tracing on? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message