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

[Nigel Horne]

Package: rsync
Version: 3.0.9-4
Severity: normal

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.

-- System Information:
Debian Release: 7.2
Architecture: armhf (armv6l)

Kernel: Linux 3.10.25+ (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rsync depends on:
ii base-files 7.1wheezy2+rpi1
ii libacl1 2.2.51-8
ii libc6 2.13-38+rpi2
ii libgcc1 1:4.7.2-5+rpi1
ii libpopt0 1.16-7
ii lsb-base 4.1+Debian8+rpi1

rsync recommends no packages.

Versions of packages rsync suggests:
ii openssh-client 1:6.0p1-4
ii openssh-server 1:6.0p1-4

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Paul Slootman]

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.


thanks,
Paul

[Simon Deziel]

On 14-03-14 02:59 PM, 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 can get the error 100% of the time by copying a 2G VM image that
changes only slightly (hostname/ip). The raw file is a sparse one.

In this example, xeon:/tmp has an older ns0.raw.

simon@laptop:~$ rsync -azSP ns0.raw xeon:/tmp/
sending incremental file list
ns0.raw
160,481,280 7% 51.00MB/s 0:00:38
rsync: [sender] write error: Broken pipe (32)

inflate returned -3 (0 bytes)
rsync error: error in rsync protocol data stream (code 12) at
token.c(548) [receiver=3.0.9]

rsync error: error in rsync protocol data stream (code 12) at io.c(837)
[sender=3.1.0]


Since the failed rsync trashed xeon:/tmp/ns0.raw, I restore the original
(old) file on the destination then re-attempted:


simon@laptop:~$ rsync -azSP ns0.raw xeon:/tmp/
sending incremental file list
ns0.raw
160,612,352 7% 51.06MB/s 0:00:38
rsync: [sender] write error: Broken pipe (32)

inflate returned -3 (0 bytes)
rsync error: error in rsync protocol data stream (code 12) at
token.c(548) [receiver=3.0.9]

rsync error: error in rsync protocol data stream (code 12) at io.c(837)
[sender=3.1.0]


Same failure but slightly later in the file. Leaving out the "-z" works
around the issue so does removing the destination's old copy.

Regards,
Simon