After much discussion, this is too risky for an SRU without much more
demonstrated analysis. It seems more appropriate for a backport.
** Changed in: rsync (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tue, Jan 03, 2017 at 05:00:09AM -, Haw Loeung wrote:
> rsync shipped in Xenial builds with the included zlib (--with-included-
> zlib=yes and -Izlib). Couldn't we SRU a fix doing the same thing as per
> https://bugs.launchpad.net/rsync/+bug/1300367/comments/6?
I am -1 on any SRU that does n
Search for --with-included-zlib in the following build logs:
Zesty -
https://launchpadlibrarian.net/293687018/buildlog_ubuntu-zesty-amd64.rsync_3.1.2-1_BUILDING.txt.gz
Xenial -
https://launchpadlibrarian.net/234647228/buildlog_ubuntu-xenial-amd64.rsync_3.1.1-3ubuntu1_BUILDING.txt.gz
Vivid -
htt
rsync shipped in Xenial builds with the included zlib (--with-included-
zlib=yes and -Izlib). Couldn't we SRU a fix doing the same thing as per
https://bugs.launchpad.net/rsync/+bug/1300367/comments/6?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Thank you for the test case. Unfortunately Ryan is no longer available
to work on this, so I'll unassign him.
Fixing this is non-trivial. I think any fix has a high risk of
regression, particularly with the permutations of rsync versions that
must interoperate. The full matrix needs to be consider
** Changed in: rsync (Ubuntu Trusty)
Status: Confirmed => Triaged
** Changed in: rsync (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
** Changed in: rsync (Ubuntu Trusty)
Status: Incomplete => New
** Changed in: rsync (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
Title:
Attaching the test data set.
If this doesn't work for some reason it is also available here:
http://people.canonical.com/~foley/lp-bug-1384503-rsync-bad-data.tgz
** Attachment added: "rsync compression error test data set"
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+attachme
We have a few servers that are exhibiting this behaviour while copying
backups sets. I cannot make any of that data available, but have tried
producing some /dev/urandom produced data files that exhibit the error
and have succeeded in getting something I hope is useful.
I discovered by accident w
** Description changed:
- Copying large (>10GB) files with rsync -z (compression) leads to a long
- hang and eventual error after transferring part of the file. The error
- is consistent. The file copies at normal speed until it reaches its
- maximum size (1.4 GB out of 20 GB for one, 6.9 GB out
I tried to rsync ubuntu 14.04 and 16.04 and got this error. But this:
> Simply move compression from rsync to ssh: -e "ssh -C"
fixed it! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
Simply move compression from rsync to ssh: -e "ssh -C"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
Title:
rsync fails on large files with compression
To manage notifications about this b
Hi, I have just published a docker compose stack to test this issue:
https://github.com/NDrive/rsync-compress-bug
Actually, I couldn't reproduce the bug with success. Maybe it only
happens in some certain files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I am also suffering from this bug with a 1GB file with the --compress
flag in Ubuntu 14.04 with Rsync 3.1.0. The bug is pretty consistent and
after I removed the compress flag I got no more broken pipes.
I will try to make this bug reproducible with Docker and publish here.
--
You received this
Hi Andrew,
Installing that version (rsync_3.1.1-3 from the Vivid repo in this case - no
dependency problems) on the machine initiating (which is also the target) the
rsync didn't fix it.
However, installing it on the source machine as well seems to have fixed the
problem.
Regards,
Tom
--
You
Sorry Charles, but a patch that is known to work just in one case isn't
really sufficient for an SRU. It is useful and I appreciate your
contribution, but alongside it we need to analyse and understand the
regression risk for other valid use cases. This is the "Regression
Potential" section of the
I attempted to SRU a patch almost a year ago. And that was after two
other people confirmed the patch worked for them.
In reply to my email Alberto Salvia Novella said on Mon, Jan 12, 2015 at 5:14 PM
C Peters:
> https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367
> Can someone nominate t
I'd still like to see this fixed, but based on Ryan's comment from when
he investigated this I don't think we can do this without a failure
case. I presume most reporters won't want to share their data publicly.
But we need a failure case in order to make progress.
Until we have one, I'm marking t
Excluding all compression options was not an acceptable solution for me.
What has worked since I initially found this problem back in August was
to install rsync from the utopic repository where the bug was fixed.
That same version (3.1.1-3) is still available in vivid and wily
unchanged as far as
Hi
I think this is fixed in future rsync versions. For Ubuntu 14.04, exclude
ALL compression when rsyncing, e.v. chancve -az to -a.
Regards,
Jan
On 11 January 2016 at 12:56, Tom Worley wrote:
> I can confirm I still get this error on Ubuntu 14.04 (all up to date)
> rsync:
> Both machines: 3.1.
I can confirm I still get this error on Ubuntu 14.04 (all up to date)
rsync:
Both machines: 3.1.0-2ubuntu0.1
File is a .sql.gz file, 1.5 GB in size, as above, --skip-compress=gz doesn't
help:
.
dbdump.sql.gz
0 0%0.00kB/s0:00:00
inflate returned -3 (0 bytes)
rsync er
It's an ongoing problem with rsync that's been around for about 10 years
or so.
Compressed files transferred with -z fail on occasion - though once you find a
file that fails, that file will always fail
I even use --skip-compress=bz2 but that doesn't work either
Last time I got it was ... today.
I also have run into this issue on a 3.1.0-2ubuntu0.1 rsync.
maglub@XXX:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS"
Can't do a "apport-collect 1384503", as I don't have a browser available
on this system. What o
I just found this report myself. I've been experiencing the problem for
a while but had to rule out other causes. This is a pretty serious bug
in an LTS release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I've attempted to reproduce this issue but I've not been able to at this
point with stock 14.04 rsync versions between two 14.04 (up-to-date)
systems. It may be highly dependent on the actual data; if you can
reproduce this with something publicly available (like a large iso
catted together multip
** Changed in: rsync (Ubuntu)
Assignee: (unassigned) => Ryan Harper (raharper)
** Also affects: rsync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: rsync (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: rsync (Ubuntu Trusty)
Status: New =>
Just discovered this bug report - after fighting with hanging backup
scripts that have worked for years, but broke after upgrading to 14.04.
I agree with Joe. Can't 3.1.1-2 be back-ported to 14.04 LTS?
This bug has now been open for just shy of 8 months
Thanks,
Kevin
--
You received this b
This is a relief, and thanks for giving your attention to this bug.
Utopic has 3.1.1-2. Can it be pushed as an update to 14.04?
Thanks!
--jh--
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
T
I installed rsync_3.1.1-2_amd64.deb from the vivid repo.
It installed without issue on trusty and, fortunately, resolves this
major bug.
Gerald
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsync (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384503
Title:
rsyn
30 matches
Mail list logo
