From owner-freebsd-scsi Tue Mar 9 7:14:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DFC2114F90 for ; Tue, 9 Mar 1999 07:14:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id HAA18008; Tue, 9 Mar 1999 07:13:37 -0800 Date: Tue, 9 Mar 1999 07:13:37 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Chris Shenton Cc: tom@tomqnx.com, scsi@FreeBSD.ORG Subject: Re: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs In-Reply-To: <87aexm7lj0.fsf@absinthe.shenton.org> 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 Yes- I added the code that tries to unload the tape if things get screwed up- but some tapes don't eject. Let's get a sense from y'all- is this a bad idea? Frankly, dump and tar and other backup programs are fantastically broken if they don't, at each open, always either explicitly position to a known locatio, or get position information and use that, or explicitly space to EOD. It seems to me that if you've lost position information you should try and force the tape out. -matt On 9 Mar 1999, Chris Shenton wrote: > [Changed CC from hackers@ to scsi@ --chris] > > Matthew Jacob writes: > > > What errors? And what 'does not honor'? I know that Tom Torrance claimed > > this happened- which I can't reproduce. > > I posted them in the previous message. It was on a 3.1-STABLE system > built from source cvsupped about 3 days ago. Here's what dmesg says: > > (sa0:ahc0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0 > (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:2c,0 > (sa0:ahc0:0:5:0): Command sequence error > (sa0:ahc0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety > > This occurs just after a dump completes and says "closing device sa0", > before the next dump begins. So it overwrites each dump file due to > the rewind. > > I don't see the PREVENT/ALLOW messages that Tom cites, but he's right > about not seeing the messages if you're using an Xterm; I missed 'em > for a day. > > Is there anything I can do to help locate the source of the bug? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message