definite data corruption in 2.5.0 with -z option

[David Bolen]

rsync at ka9q.net [rsync at ka9q.net] writes:

> After I sent my note, I ran some more experiments and found the
> problem goes away if I use the default checksum blocksize. So the
> problem occurs *only* if I use a large blocksize (65536) *and* enable
> compression.

Should have read ahead - this is probably the problem I was recalling
in my last reply.  There was some reason I tended to keep my variable
block sizes that my scripts were picking <= 32K or so.

If that's it, then I doubt it's the "bit length overflow" issue since
I was running into this back with a modified 2.4.3.

-- David

/-----------------------------------------------------------------------\
 \               David Bolen            \   E-mail: db3l at fitlinxx.com  /
  |             FitLinxx, Inc.            \  Phone: (203) 708-5192    |
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150     \
\-----------------------------------------------------------------------/