Date: Tue, 29 Aug 2000 13:00:40 +0930 From: Greg Lehey <grog@lemis.com> To: Matthew Jacob <mjacob@feral.com> Cc: Sam <freep@thecity.sfsu.edu>, freebsd-scsi@FreeBSD.ORG Subject: Re: "tape is now frozen" Message-ID: <20000829130040.Q11422@wantadilla.lemis.com> In-Reply-To: <Pine.BSF.4.10.10008081636150.87492-100000@beppo.feral.com>; from mjacob@feral.com on Tue, Aug 08, 2000 at 04:39:03PM -0700 References: <20000809090336.F13974@wantadilla.lemis.com> <Pine.BSF.4.10.10008081636150.87492-100000@beppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 8 August 2000 at 16:39:03 -0700, Matt Jacob wrote: >> >> Indeed, it looks like he omitted the message that we most wanted to >> see. >> >> Let me repeat here that I find this *very* irritating. It happens, >> for example, if I try to read a block which is too long. There's no >> way to know the length of a tape block in advance, so this is >> relatively easy to get, particularly with DDS-4 drives, and it > > This error should not occur if you're in variable block mode. If you > set the drive in fixed block mode and read a block that's too large, > the tape driver cannot know where the tape heads are located. It's > that simple. It's not that simple. If it happens in the middle of the tape, I need to rewind the bloody thing to recover. At least an fsf or bsf should be sufficient. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers 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?20000829130040.Q11422>