Delivered-To:	listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<36C2B573.EFEDE54@uni-duesseldorf.de>
Date:	Thu, 11 Feb 1999 11:48:19 +0100
From:	Stipe Tolj <tolj AT uni-duesseldorf DOT de>
Organization:	Department of Economical Computer Science, University of Cologne,
	Germany
X-Mailer:	Mozilla 4.05 [de]C-NECCK (Win95; I)
MIME-Version:	1.0
To:	Frank McIngvale <frankm AT HiWAAY DOT net>
CC:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: More corruption [Re: Problems with ncftp]
References:	<Pine DOT OSF DOT 4 DOT 02 DOT 9902101508240 DOT 26393-100000 AT fly DOT HiWAAY DOT net>

> 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 AT uni-duesseldorf DOT 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 AT sourceware DOT cygnus DOT com

- Raw text -