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 X-Lotus-FromDomain: GROS From: colin DOT mcgeoch AT gro-scotland DOT gsi DOT gov DOT uk To: cygwin AT sourceware DOT cygnus DOT com Message-ID: <80256931.0038E544.00@gro-scotland.gsi.gov.uk> Date: Fri, 4 Aug 2000 11:21:26 +0100 Subject: TAR FAILURE ON LARGE FILE (NT) Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=GJLXykxgLGj0Mth2fkHmkQ1gQVeQcAbxFejcdUbJDV7KTY0WAFrER1XX" Content-Disposition: inline --0__=GJLXykxgLGj0Mth2fkHmkQ1gQVeQcAbxFejcdUbJDV7KTY0WAFrER1XX Content-type: text/plain; charset=us-ascii Content-Disposition: inline Hi, When I run --0__=GJLXykxgLGj0Mth2fkHmkQ1gQVeQcAbxFejcdUbJDV7KTY0WAFrER1XX Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable ?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 re= late to a different problem on much smaller files(25MB). I have only recently sta= rted 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 = --0__=GJLXykxgLGj0Mth2fkHmkQ1gQVeQcAbxFejcdUbJDV7KTY0WAFrER1XX Content-Type: text/plain; charset=us-ascii -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com --0__=GJLXykxgLGj0Mth2fkHmkQ1gQVeQcAbxFejcdUbJDV7KTY0WAFrER1XX--