This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: More corruption [Re: Problems with ncftp]
- To: Frank McIngvale <frankm@HiWAAY.net>
- Subject: Re: More corruption [Re: Problems with ncftp]
- From: Stipe Tolj <tolj@uni-duesseldorf.de>
- Date: Thu, 11 Feb 1999 11:48:19 +0100
- CC: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Organization: Department of Economical Computer Science, University of Cologne, Germany
- References: <Pine.OSF.4.02.9902101508240.26393-100000@fly.HiWAAY.net>
- Sender: cygwin-owner@sourceware.cygnus.com
> Hm, it's apparently not just a problem with ncftp.
> The following also causes file corruption:
>
> $ bzip2 -9k bigfile
> $ bzip2 -dc bigfile.bz2 | bzip2 -9 > out.bz2
>
> bigfile = 21,301,412 bytes
> bigfile.bz2 = 3,338,162 bytes
> out.bz2 = 3,351,827 bytes (!!!)
>
> $ bzip2 -t out.bz2
>
> out.bz2: data integrity (CRC) error in data
>
> Now, since bigfile.bz2 is okay, it's not a problem
> with bzip2 or any text/binary issues with the
> filesystem, right? Something must be going wrong
> during the pipeline in the second step.
>
> As an additional test, I tried this with a file
> of size 387,259 bytes, and everything was OK, so
> there appears to be some size threshold where this
> error occurs.
>
> Again, this is B20.1, egcs-1.1.1, tcsh 6.08.
have you noticed the same effect within bash?
Regards,
Stipe
--
Stipe Tolj <tolj@uni-duesseldorf.de>
Cygwin Porting Project -- "We build UNIX on top of Windows"
http://www.student.uni-koeln.de/cygwin/
Department of Economical Computer Science
University of Cologne, Germany
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com