Bug#741628: rsync dies with "inflate returned -3"

[Nigel Horne]

On 14/03/2014 14:59, Paul Slootman wrote:

On Fri 14 Mar 2014, Nigel Horne wrote:

When using the -z flag of rsync, it dies with

inflate returned -3 (0 bytes)
rsync error: error in rsync protocol data stream (code 12) at token.c(548) 
[receiver=3.0.9]
rsync: writefd_unbuffered failed to write 4 bytes to socket [generator]: Broken 
pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1532) 
[generator=3.0.9]

Removing the -z flag fixes it.

Is this always, or only with certain data? If it's always, then it's
probably related to the architecture / build, as I'm sure I would have
been deluged by vast amounts of complaints if rsync always failed with
-z ...

If it's only with certain data, it would be great if you could supply a
minimal case to reproduce the problem.

I've only seen it with very large files (say 1 or 2 G in size). That may or may not be relevant. FWIW, I've also seen it on a PPC machine. I don't know if that's relevant or not. Both machines were copying from a x64_64 machine.

thanks,
Paul

Regards,

-Nigel

smime.p7s
Description: S/MIME Cryptographic Signature