Date: Thu, 18 Jan 2001 12:00:38 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz> Cc: Eric Lee Green <eric@estinc.com>, freebsd-scsi@FreeBSD.org Subject: Re: Troubles with Mammoth2 if there is a tape error Message-ID: <Pine.LNX.4.21.0101181159010.840-100000@zeppo.feral.com> In-Reply-To: <20010118195154.A33758@dcse.fee.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 18 Jan 2001, Cejka Rudolf wrote: > > Eric Lee Green wrote (2001/01/17): > > Well, first I would say that it is a bug in the firmware that you're > > testing -- after the first time that the tape drive attempts to write that > > block on tape, it should be reported as an immediate error, not as a > > deferred error. > > Hmm, so what to do now? > > Does anybody have close relationship with Exabyte? > > At this time I'm sure that I can not kill dd process and in > /var/log/messages there are no immediate errors - just deferred errors. > But I still do not know, what commands flow over SCSI bus (is CAMDEBUG > sufficient?). Yes- in this case. > > > have a deferred error (it's inherent in buffered tape i/o), but the drive > > is supposed to know for further writes that it should send an immediate > > error. > > If I can not kill -9 dd, are any further writes without dd possible? Well, I can annoy the frick out of even more people and declare that Deferred Media errors *also* make the tape state frozen (thus nuking dd and causeing you to do an EOM, REWIND or OFFLINE to get state back to a known place (actually, setting specific block position should do it too- need to remember to do this...).... Was wollen sie? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0101181159010.840-100000>