From owner-freebsd-scsi Thu Jan 18 12:11:18 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E439437B404; Thu, 18 Jan 2001 12:11:00 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA00838; Thu, 18 Jan 2001 11:58:41 -0800 Date: Thu, 18 Jan 2001 12:10:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: freebsd-scsi@FreeBSD.org Subject: Re: Troubles with Mammoth2 if there is a tape error In-Reply-To: <200101182023.f0IKNNQ00888@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yes, but also given how many people turn purple in the face and scream at you me on this very topic, I suspect y'all will understand if I'm a bit reluctant to do so..... -matt > > 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...).... > > Well, I'm inclined to think this is the right thing to do. > > A 'deferred media error' basically just tells you that the tape you've > just written is now junk (because it's corrupt), and the only correct > actions I can think of are: > > - eject and discard > - rewind, erase and retry > > since the drive will, in theory, already have exhausted its > error-compensation capability so offering anything that just tries to > allow re-writing the block isn't going to help... > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message