Compression error? -- "Inflate (token) returned -5"

[Bas van Schaik]

Hi all,

A little less than a year ago I replied to this thread, but I'm still
having similar problems. Again, the "Inflate (token) returned -5" error
occurred while syncing a file:
> 2008/09/04 22:11:20 [7017] name lookup failed for 172.26.3.224: Name
> or service not known
> 2008/09/04 22:11:20 [7017] connect from UNKNOWN (172.26.3.224)
> 2008/09/04 22:11:20 [7017] rsync to backups/tetra-networking/latest/
> from wallis at UNKNOWN (172.26.3.224)
> 2008/09/04 22:11:20 [7017] receiving file list
> 2008/09/04 22:11:47 [7017] inflate (token) returned -5
> 2008/09/04 22:11:47 [7017] rsync error: error in rsync protocol data
> stream (code 12) at token.c(476) [receiver=2.6.9]
> 2008/09/04 22:11:47 [7017] rsync: connection unexpectedly closed
> (3301591 bytes received so far) [generator]
> 2008/09/04 22:11:47 [7017] rsync error: error in rsync protocol data
> stream (code 12) at io.c(454) [generator=2.6.9]
Above you see a snippet of the server log, the client only reports:
> rsync: writefd_unbuffered failed to write 1 bytes [sender]: Connection reset by peer (104)
> rsync: connection unexpectedly closed (291575 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(454) [sender=2.6.9]

And again, when using triple verbose mode the last "match at" lines
almost matches the filesize of the file to transfer:
> (...)
> match at 68541840 last_match=68541840 j=8278 len=8280 n=0
> match at 68550120 last_match=68550120 j=8279 len=8280 n=0
> match at 68558400 last_match=68558400 j=8280 len=250 n=0
> rsync: writefd_unbuffered failed to write 1 bytes [sender]: Connection
> reset by peer (104)
> (...)
> $ ls -la
> "/backups/tetra-networking/latest/10.23.23.1/w/home/connie/Foto's BBQ
> 23-06-06.zip"
> -rwxr--r-- 9 rsync nogroup 68558650 2008-08-19 23:42
> /backups/tetra-networking/latest/10.23.23.1/w/home/connie/Foto's BBQ
> 23-06-06.zip
(note that 68558400 + 250 = 68558650)

The file to be transferred is quite small: about 66MB. However, if I try
to sync the file on its own (not the whole directory structure) the
error does not occur! The tail of the output of the successful rsync:

> $ rsync -ratzvvv --delete --compress-level=9 --timeout=3600
> --password-file=/backups/rsync_wallis.secret client-original.zip
> wallis at hilbert::tmp/
> (...)
> match at 68550120 last_match=68550120 j=8279 len=8280 n=0
> match at 68558400 last_match=68558400 j=8280 len=250 n=0
> done hash search
> sending file_sum
> false_alarms=0 hash_hits=8281 matches=8281
> sender finished client-original.zip
> send_files phase=1
> send_files phase=2
> send files finished
> total: matches=8281  hash_hits=8281  false_alarms=0 data=0
>
> sent 104 bytes  received 58005 bytes  16602.57 bytes/sec
> total size is 68558650  speedup is 1179.83
> _exit_cleanup(code=0, file=main.c, line=977): about to call exit(0)

Clearly it has something to do with the context which the file is in and
not the contents of this single file. The only known workaround I know
is disabling the compression... FYI: both client and server are using
rsync 2.6.9 (from Ubuntu Hardy Heron). Does anyone have more information
regarding this issue?

Kind regards,

  -- Bas