From owner-freebsd-scsi Tue Aug 8 17: 9: 1 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 1F35437B901 for ; Tue, 8 Aug 2000 17:08:56 -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 RAA22168; Tue, 8 Aug 2000 17:08:54 -0700 Date: Tue, 8 Aug 2000 17:08:58 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sam Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: "tape is now frozen" In-Reply-To: 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 I would appreciate knowing what the actual error messages were in your /var/adm/messages. It's just barely conceivable that reading from known end of recorded media could be *assumed* to not really change tape position, but I'd rather be safe than sorry. Looking at your original email, I see you backed up, using the no-rewind device. Then you tried to restore (without a rewind). Well, yes, the tape driver won't know where you are because you ran past recorded media. The problem here is really then with restore- you were expecting restore to rewind and read from the first file. Cursory examination of the code shows that if the dump number is one, it doesn't do this. Sounds like, woohoo, restore's got another bug. -matt On Tue, 8 Aug 2000, Sam wrote: > We got it to work by setting the density to the density of the tape: > -d 97000 for dds3 > -d 61000 for dds2 and dds1 > > thanks for all your help, > Sam > > -----Original Message----- > From: owner-freebsd-scsi@FreeBSD.ORG > [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of Matthew Jacob > Sent: Tuesday, August 08, 2000 4:39 PM > To: Greg Lehey > Cc: Sam; freebsd-scsi@FreeBSD.ORG > Subject: Re: "tape is now frozen" > > > > > > 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 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message