aims team mailing list archive

[Robie Basak <1384503@xxxxxxxxxxxxxxxxxx>]

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 SRU paperwork, together with the SRU
Verification process that is documented. I asked for this in comment #8
in the same bug, but nobody responded.

This isn't unnecessary or bureaucratic red tape. The process is there to
ensure that we do not regress millions of users by trying to fix a bug
that doesn't affect them.

I'm not willing to upload your patch for SRU review because I don't know
what other behaviour it might regress. In order to perform the required
analysis, a complete failure case (which in this case needs the correct
test data for a failure case) would be most useful.

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to a duplicate bug report (1431709).
https://bugs.launchpad.net/bugs/1384503

Title:
  rsync fails on large files with compression

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Trusty:
  Incomplete

Bug description:
  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 of 29 GB for
  another).  Then nothing happens for a while (many minutes).  Finally,
  there is an error:

  [....]
  jh/.VirtualBox/win7/win7.vbox
  jh/.VirtualBox/win7/win7.vbox-prev
  jh/.VirtualBox/win7/win7.vdi
  rsync: [sender] write error: Broken pipe (32)
  rsync error: error in rsync protocol data stream (code 12) at io.c(837) [sender=3.1.0]

  In this case, 6.9 GB of 29 GB transferred.  Without -z, it works.

  See the following upstream report, with a comment at the end from the
  rsync maintainer:

  https://bugzilla.samba.org/show_bug.cgi?id=10372

  According to this report, version 3.1.0 (included in 14.04) uses a
  different compression package from prior versions.  Prior versions did
  not have this problem for me using the same command on the same
  systems. Both hosts ran Ubuntu 11.10 at the time, and all run 14.04
  now, in each case with all updates applied, Intel hardware.  Network
  connection between them is gigabit ethernet through one switch.  A
  shell ssh between them in a terminal works and stays up during the
  failure, so it is not a network issue.  There are no relevant entries
  in syslog on either machine.  There is sufficient capacity on the
  receiving disk.  All filesystems are ext4.

  rsync command:

  /usr/bin/rsync -aHSxvz --delete --stats --exclude=lost+found
  --exclude=.gvfs --exclude=/nonlaptop /home/
  backup.host.edu:/bu/host/home/

  (yes, I changed the machine names)

  Current release (both hosts):

  Description:	Ubuntu 14.04.1 LTS
  Release:	14.04

  Current package (both hosts):

  rsync:
    Installed: 3.1.0-2ubuntu0.1
    Candidate: 3.1.0-2ubuntu0.1
    Version table:
   *** 3.1.0-2ubuntu0.1 0
          500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
          500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
          100 /var/lib/dpkg/status
       3.1.0-2 0
          500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  Thanks,

  --jh--

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+subscriptions