From owner-freebsd-questions Wed Jan 6 18:50:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16108 for freebsd-questions-outgoing; Wed, 6 Jan 1999 18:50:06 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16069 for ; Wed, 6 Jan 1999 18:50:01 -0800 (PST) (envelope-from adg@infowest.com) Received: (from root@localhost) by infowest.com (8.8.8/8.8.8) id TAA02192 for questions@freebsd.org; Wed, 6 Jan 1999 19:49:49 -0700 (MST) Date: Wed, 6 Jan 1999 19:49:49 -0700 (MST) From: "Aaron D. Gifford" Message-Id: <199901070249.TAA02192@infowest.com> To: questions@FreeBSD.ORG Subject: Re: Why won\'t TAR cooperate\? Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Aaron D. Gifford" wrote: >> >> Okay, call me a nutcase, but I can't figure out why TAR always bails out >> at exactly 255328256 bytes written of a huge 4GB file I'm trying to dump >> to tape. At first, it would quit with an error so I downloaded the latest >> GNU tar from GNU's FTP site, installed and compiled it. It too bails out >> at the same spot, but without an error. >> >> Any ideas anyone? >> To which Roman Katsnelson replied: >hi nutcase, > >can the tape be out of space at that point? > >hth, >roman > I wish that were the case, but this is a new DLTtapeIV with a capacity of 35GB uncompressed or 70GB compressed on the DLT7000 drive. A paltry 4GB file should easily fit. That said, could this be a case of tar for some reason thinking the tape was full? How would I find out if this is the case? How would I tell tar that the tape's capacity is MUCH greater than the 250MB by a factor of 100 or more? Ideas and suggestions welcome! Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message