From owner-freebsd-scsi Tue Feb 20 12:14:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 29FDD37B4EC for ; Tue, 20 Feb 2001 12:14:44 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.11.2/8.11.2) with ESMTP id f1KKEes72958 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Tue, 20 Feb 2001 21:14:41 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.11.2/8.11.2) id f1KKEet17640; Tue, 20 Feb 2001 21:14:40 +0100 (CET) Date: Tue, 20 Feb 2001 21:14:40 +0100 From: Cejka Rudolf To: Matthew Jacob Cc: Eric Lee Green , freebsd-scsi@FreeBSD.org Subject: Re: Troubles with Mammoth2 if there is a tape error Message-ID: <20010220211440.A16566@dcse.fee.vutbr.cz> References: <20010118195154.A33758@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Thu, Jan 18, 2001 at 12:00:38PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Finally, I have succeed to log kernel messages with CAMDEBUG on. All files are in ftp://ftp.FreeBSD.cz/pub/FreeBSD-local/camdebug/: SYSTEM - kernel configuration tapewtest - test script messages.gz - messages file, where (time stamps are good search patterns :-): 19:41:22 .. 19:41:27: Generated messages when CAMDEBUG is off after tape error 19:43:19: Reboot with kernel in which CAMDEBUG is on ... 20:12:38: Messages until tape error 20:12:38 ... 20:12:54: Why is there such big delay? 20:12:54 ...: Messages after tape error Please, could you look at it if you can say something more than before? On thursday, I expect that arrive service-man directly from Exabyte, but I do not know, what I should say to him. Thanks. Matthew Jacob wrote (2001/01/18): > 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 > > -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message