From owner-freebsd-scsi Tue Aug 8 16:39:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CE42237B868 for ; Tue, 8 Aug 2000 16:39:09 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA22030; Tue, 8 Aug 2000 16:38:59 -0700 Date: Tue, 8 Aug 2000 16:39:03 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Sam , freebsd-scsi@FreeBSD.ORG Subject: Re: "tape is now frozen" In-Reply-To: <20000809090336.F13974@wantadilla.lemis.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 > > 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. Set your tape drive to variable mode. If the error occurs then, it certainly is wrong and should be fixed. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message