Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Aug 2000 20:36:42 -0700 (PDT)
From:      Matthew Jacob <mjacob@feral.com>
To:        Greg Lehey <grog@lemis.com>
Cc:        Sam <freep@thecity.sfsu.edu>, freebsd-scsi@FreeBSD.ORG
Subject:   Re: "tape is now frozen"
Message-ID:  <Pine.BSF.4.21.0008282031330.36166-100000@beppo.feral.com>
In-Reply-To: <20000829130040.Q11422@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On Tue, 29 Aug 2000, Greg Lehey wrote:

> 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.

So you space a filemark. Where specfically on the tape are you given you've
lost knowledge of where you are? The whole point of rewind, eom or offline is
to bring the tape to a *known* place. Spacing one filemark is not sufficient.

I thought for awhile about allowing the use of rdhpos/sethpos to allow
for unfreezing.

You're also, again, begging the question as to why it has occurred. It has
occurred because there was an I/O error, or you're not using the tape
correctly (fixed block mode and you don't issue the correct read size).

I keep on getting pushback on this. Perhaps an 'unfreeze' ioctl, call it
MTIOSUICIDE, is in order. Not.


-matt




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.BSF.4.21.0008282031330.36166-100000>