Date: Thu, 18 Jan 2001 12:10:59 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Mike Smith <msmith@FreeBSD.org> Cc: freebsd-scsi@FreeBSD.org Subject: Re: Troubles with Mammoth2 if there is a tape error Message-ID: <Pine.LNX.4.21.0101181210140.840-100000@zeppo.feral.com> In-Reply-To: <200101182023.f0IKNNQ00888@mass.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0101181210140.840-100000>