From owner-freebsd-current  Wed Apr 28 13:45:43 1999
Delivered-To: freebsd-current@freebsd.org
Received: from neunacht.netgsi.com (neunacht.netgsi.com [192.55.203.174])
	by hub.freebsd.org (Postfix) with ESMTP id D7AB8151A8
	for <current@FreeBSD.ORG>; Wed, 28 Apr 1999 13:45:38 -0700 (PDT)
	(envelope-from cjohnson@neunacht.netgsi.com)
Received: (from cjohnson@localhost)
	by neunacht.netgsi.com (8.9.2/8.9.2) id QAA38050;
	Wed, 28 Apr 1999 16:45:17 -0400 (EDT)
	(envelope-from cjohnson)
From: "Christopher T. Johnson" <cjohnson@neunacht.netgsi.com>
Message-Id: <199904282045.QAA38050@neunacht.netgsi.com>
Subject: Re: Further on tape & CAM problems
In-Reply-To: <199904281938.VAA01921@yedi.iaf.nl> from Wilko Bulte at "Apr 28, 99 09:38:45 pm"
To: wilko@yedi.iaf.nl (Wilko Bulte)
Date: Wed, 28 Apr 1999 16:45:17 -0400 (EDT)
Cc: dillon@apollo.backplane.com, shocking@prth.pgs.com,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> As Christopher T. Johnson wrote ...
> 
> > REGARDLESS!
> > 	The drive is reporting an error condition and that error is NOT
> > 	getting back to user land.  I've verified the problem with amdump
> 
> Oh? Where/what is the error, does the console tell you? 

Sorry, no error reported, just the lights.  Amber light, no green solid.
Either the kernel has the device "active" OR it is an error indicator.
Exabyte is known for doing that.

> 
> > 	amflush and dd.  In ALL cases once the amber light goes on solid
> > 	systat -vmstat shows a solid 1.4MB/second data transfer into
> > 	never never land.
> 
> That sounds like a bug. But it could be CAM not understanding that the
> 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte
> lockup..

Yep, been there done that.  But these drives have been rock solid.  It is
not the case of putting in a new, unknown drive and finding out that
it is a little strange.  It is the case where I have a hardware configuration
that has been stable that suddenly isn't.

The original change is the upgrade to 4.0-CURRENT.  After that drive
"failed" I took our back up drive and put it into production and got exactly
the same failure mode.

Here is the sequence that I just did:
	Old working tape.
	mt erase &
		1hr 30minutes or so later
		Drive makes sounds of tape stopping.
	Amber light comes on
	mt erase reports done (no errors)
	mt rewind
		mt: /dev/nrsa0: Device busy
	push button on face plate
		amber light goes out, tape noises.
		Green light comes on.
	mt rewind 
		tape is ejected at the same place as all the other failures.
	push tape back into drive
		Drive is ejected.
	manually rewind tape (Yeah Yeah, I know don't do it but the exabyte
		ejects the tape each time it is reinserted until I have
		it mostly rewound)
repeat with new tapes old tapes and almost new tapes.... Same thing
	Chris
> 
> Groeten / Cheers,
> 
> |   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
> |/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	http://www.freebsd.org
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message