From owner-freebsd-scsi Fri Mar 12 8:46:52 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 C9F36152DF for ; Fri, 12 Mar 1999 08:46:46 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id IAA00290; Fri, 12 Mar 1999 08:45:28 -0800 Date: Fri, 12 Mar 1999 08:45:28 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Christian Weisgerber Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Wangtek 51000HT tape drive In-Reply-To: <7carem$sn1$1@mips.rhein-neckar.de> 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 > Matthew Jacob wrote: > > > Did you run a CAMDEBUG kernel? That should then print out: > > I have now. Yes, the quirk matches. > > > fctblab.nas.nasa.gov > cpio -iF $TAPE > > 4070 blocks > > fctblab.nas.nasa.gov > mt stat > ... > > File Number: 0 Record Number: 4070 > > fctblab.nas.nasa.gov > mt fsf > > fctblab.nas.nasa.gov > mt stat > ... > > File Number: 1 Record Number: 0 > > fctblab.nas.nasa.gov > cpio -iF $TAPE > > 67 blocks > > Yes, exactly. You shouldn't need to do an explicit fsf, should you? Unless you are explicitly using either a AT&T style tape behaviour or have an application that keeps reading until it gets an error or gets an indication that less data was moved than asked for, yes. Or...[see below] > > > > In real life, of course, I use something like buffer(1) or team(1). So > > And where are these entities? Ports collection? > > team is a port, buffer will be (again) as soon as somebody gets around > to committing ports/10549. > > > Did it used to work that CPIO and/or tar would always end up in the next > > tape file? > > I think so. I believe, in fact, that AT&T invented the 'space to next file on close' behaviour *because* CPIO doesn't do this. > Actually, now that you're asking, I think it rather was like this: > > $ tar x > ... # extracts first archive > $ tar x # does nothing, apparently gets EOF > $ tar x > ... # extracts second archive That counts as part of the description above. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message