Date: Thu, 11 Dec 1997 14:00:11 +0800 From: Greg Lehey <grog@lemis.com> To: Allan Alford <aa@jump.net> Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Wangtek 51000HT 1/4" SCSI-2 QIC 1000 Message-ID: <19971211140011.44835@lemis.com> In-Reply-To: <348F72F6.6B37@jump.net>; from Allan Alford on Wed, Dec 10, 1997 at 10:58:30PM -0600 References: <348F0FB9.C6C@jump.net> <19971211011508.60795@uriah.heep.sax.de> <348F72F6.6B37@jump.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 10, 1997 at 10:58:30PM -0600, Allan Alford wrote: > J Wunsch wrote: > >> How exactly do you do it? It works for me. >> > > I've been using the following syntax in my script: > > tar -cv /dev/nrst0 /foo > tar -cv /dev/nrst0 /bar > tar -cv /dev/nrst0 /foobar > > When I check the tape the next morning, I do: > > mt rewind > (tape already seems to be rewound) > tar -tv > (yields the tar of foobar - the last from the list) > mt fsf 1 > (nothing seems to happen) > tar -tv > (yields the tar of foobar - the last from the list) > > Is there a quicker way to test and make sure that the /nrst0 device > really is no rewind? Some way to copy something directly, perhaps? > > cpio, maybe? I've only ever worked with DAT in the past and have > never had these problems. I do pretty much exactly this for my nightly backup, and it works fine. I'd guess that this is a driver bug, not a tar bug. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971211140011.44835>