Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 May 2007 00:41:36 -0400
From:      David Banning <david+dated+1178599299.38573d@skytracker.ca>
To:        David Kelly <dkelly@hiwaay.net>
Cc:        questions@freebsd.org
Subject:   Re: can't zip large files 2gb >
Message-ID:  <20070503044136.GA57871@skytracker.ca>
In-Reply-To: <20070502190950.GA84501@Grumpy.DynDNS.org>
References:  <20070501195825.GA10269@skytracker.ca> <20070502093757.GA2835@kobe.laptop> <20070502162657.GA21779@skytracker.ca> <20070502171723.GA1615@kobe.laptop> <20070502180815.GA50145@skytracker.ca> <20070502190950.GA84501@Grumpy.DynDNS.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> I haven't been paying 100% attention. Just how does it fail? What do you
> mean by "corrupt"?
> 
> Does the process run to completion?

All programs zip with no errors. On reading;

root# bzip2 -t zippedfile.bz2
bzip2: 3s1.com-smartstage_ftp-full-20070502-0125AM.1b.tar.bz2: 
data integrity (CRC) error in data

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

- gzip also sites a "crc" error  
- can't remember rzip's error, (it does output an error.)
- uncompress goes without echoing error but tar expanded is
  not able to be untarred.

> Are the output zip files reasonable in size?

The zipped file size seems reasonable in each case.

> Are the expanded files reasonable in size? 

expanding will not complete, except uncompress, which expands the 
file to the original size, plus 6 bites, then the tar file expanded
is unreadable.

If so where does the mismatch
> start?

on expanding, it seems the error happens near or at the end of
the expanding process before halting and exiting with error,
that is if I attempt to read the file with "tar -tzf filename.tgz"
in gzip's case or "tar -tyf filename.bz2 in bzip2's case.

> 
> Is the problem always in the same place for the same input file?

Pretty much, but I can't say if it is exactly the same in each case.

I am going to attempt swapping memory and see if the error continues.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20070503044136.GA57871>