From owner-freebsd-scsi Thu Jan 18 12: 9: 5 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D9A4E37B404 for ; Thu, 18 Jan 2001 12:08:47 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0IKNNQ00888; Thu, 18 Jan 2001 12:23:23 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101182023.f0IKNNQ00888@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.org Subject: Re: Troubles with Mammoth2 if there is a tape error In-reply-to: Your message of "Thu, 18 Jan 2001 12:00:38 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 12:23:23 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message