Date: Wed, 06 Jun 2007 22:37:21 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Robin Gruyters <r.gruyters@yirdis.nl> Cc: freebsd-stable@freebsd.org Subject: Re: Unrecognized archive format with RELENG_6_2 and RELENG_6 Message-ID: <46679991.4080302@freebsd.org> In-Reply-To: <20070606084406.8v6nkbtv9csgs880@server.yirdis.nl> References: <20070601114047.z6qgi686os4ogw4o@server.yirdis.nl> <200706020852.21208.doconnor@gsoft.com.au> <20070604101603.f0ki85am800wso0k@server.yirdis.nl> <200706052131.44320.doconnor@gsoft.com.au> <46658EEB.5000008@freebsd.org> <20070606084406.8v6nkbtv9csgs880@server.yirdis.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> This morning I have revert libarchive (src/lib/libarchive) and tar >>> (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) >>> it works fine now. > > After that I try to read/list the tar from tape with tar -t: > $ sudo tar -tf /dev/sa0 > archive.dmp > tar: Unrecognized archive format: Inappropriate file type or format > > But when I extract the archive from tape, it works perfectly: > $ sudo tar -xvf /dev/sa0 > x archive.dmp What SCSI controller are you using? This could conceivably be an issue with a particular SCSI controller. A few lines from 'dmesg' could help here. If I must, I suppose I could make 'tar' never try to seek if it's talking directly to a device. That would penalize devices that can seek, so I'd rather find an alternate solution. Tim Kientzle P.S. In the meantime, of course, tar from 6.1 and gtar should both work in this situation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46679991.4080302>