The other hint in the debian bug is that with rsync 3.1.1 (upgraded from
3.1.0) it works. In this bug, 3.1.1 was at the receiving side, and 3.1.0
is the sender.
One of the changes in 3.1.1 is a new compression stryle, triggered by -zz. A
test to see if this gets rid of the problem, since the server side is 3.1.1, is
to use that option from the trusty (14.04) side. Example:
$ rsync -avHP -zz .bashrc xenial-rsync.lxd:/tmp
sending incremental file list
.bashrc
3,828 100% 0.00kB/s 0:00:00 (xfr#1, to-chk=0/1)
sent 1,861 bytes received 35 bytes 3,792.00 bytes/sec
total size is 3,828 speedup is 2.02
Here the machine running the above rsync command is trusty, with rsync
3.1.0. It doesn't understand -zz, but passes it along to the server,
which is xenial and is running 3.1.1.
Could people affected by this bug see if that -zz option (instead of
just -z) helps?
** Changed in: rsync (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1751489
Title:
rsync dies with "inflate returned -3 (0 bytes)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1751489/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
