[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

** Changed in: rsync Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title: rsync -u --inplace --partial -a can't resume transfer To manage notifications about

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

Thanks Nahuel! We're doing some retriage and cleanup of old bugs, and I stumbled on this one :-) I linked your upstream bug report to this bug, Launchpad will keep its status in sync. You may have noticed that I didn't set the status of this bug to Wontfix but to Opinion ("Doesn't fit with the

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

** Also affects: rsync via https://github.com/WayneD/rsync/issues/236 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title: rsync -u

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

Reported to upstream at: https://github.com/WayneD/rsync/issues/236 ** Bug watch added: github.com/WayneD/rsync/issues #236 https://github.com/WayneD/rsync/issues/236 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

Hello Paride, 4 years have passed from my initial report, I forgot completely about this bug :) Fine, I will post this issue to upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title:

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

Hello Nahuel, According to your reasoning I assume the "root" issue should still affect the versions of rsync shipped with the newer Ubuntu releases. I agree it would be nice for the behavior you describe to be documented, but I don't think it's worth patching the Ubuntu package for it. I

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

** Changed in: rsync (Ubuntu) Status: New => Triaged ** Changed in: rsync (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title: rsync -u

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

Researching more, I see POSIX has NO way to disable mtime updating while calling write()'s, so there is no way to atomically leave a partial file with an mtime=0 mark while using --inplace. "rsync --update --partial" (no --inplace) can do it because it transfers first to a temporal file, then

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

rsync version: rsync version 3.1.1 protocol version 31 ubuntu version: 3.1.1-3ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title: rsync -u --inplace --partial -a can't resume

[Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer

A reproducible test: ~$ cd /tmp/ /tmp$ mkdir a b /tmp$ cd a /tmp/a$ head -c 10 /dev/urandom > test /tmp/a$ ls -l test -rw-r--r-- 1 nahuel nahuel 10 Jan 27 18:27 test /tmp/a$ cd ../b /tmp/b$ timeout 3 rsync -u --inplace --partial --bwlimit=2k --progress -va ../a/test . sending incremental