Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <200008041938.OAA15516@mail1.sunflower.com> From: "Doug Wyatt" To: cygwin AT sourceware DOT cygnus DOT com Date: Fri, 4 Aug 2000 14:38:24 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Tar failure on large file (NT) Reply-to: dwyatt AT sunflower DOT com CC: colin DOT mcgeoch AT gro-scotland DOT gsi DOT gov DOT uk In-reply-to: <80256931.0038E544.00@gro-scotland.gsi.gov.uk> X-mailer: Pegasus Mail for Win32 (v3.12b) This looks like a 32/64-bit issue. Try entering 4415176704 in the NT calculator in decimal mode, then click on Hex. Supposedly, GNU tar 1.13 has extended tar's ability to handle file sizes > 2GB so you might try building and using that. Using some combination with gzip may provide a workaround, but probably not. Regards, Doug Wyatt > Hi, > When I run ?tar -cvf - sourcefilename>targetfilename? (in a DOS window) on a > file of size 4,415,176,704 bytes, the resulting TAR file only has size > 120,217,600 bytes , although no error messages are given. In contrast, the same > command works successfully on a smaller file (eg 120,217,600 bytes). > > The only archives reference I have found on tar/large files seems to relate to a > different problem on much smaller files(25MB). I have only recently started with > cygnwin, so apologies if I have nissed something obvious. > > Is there a file size limit on using tar ? > Could tar be finding a byte which fools it into thinking it has reached the end > of the file when it hasn?t ? > > Thanks > Colin > > > > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com