rsync - Jul 2016 - [Bug 12030] New: rsync leaves temporary files when transfer is interrupted.

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

            Bug ID: 12030
           Summary: rsync leaves temporary files when transfer is
                    interrupted.
           Product: rsync
           Version: 3.1.2
          Hardware: All
                OS: FreeBSD
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: yuri at rawbw.com
        QA Contact: rsync-qa at samba.org

When the transfer 'rsync -a dir remote:.' is interrupted and then reran,
it
leaves the temporary files with a period as a prefix and suffixes like this:
.T5umN0

It will be great if rsync first cleaned up the previously left temp files that
have the same name pattern.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

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

--- Comment #1 from Kevin Korb <rsync at sanitarium.net> ---
By default rsync does delete the incomplete file when it is aborted.  The
override for that is --partial (which is implied by -P).

However, it also depends on how the rsync is interrupted.  If it crashed or was
killed then it wouldn't have the opportunity to clean up.  If network
connectivity was lost then it is possible that the sshd and rsync are actually
still running waiting to receive the rest of that file.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

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

--- Comment #2 from Yuri <yuri at rawbw.com> ---
The intelligent way to handle this is to verify the leftover temporary file
content with partial checksums and reuse it if the content is the same as an
incoming file.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

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

--- Comment #3 from Kevin Korb <rsync at sanitarium.net> ---
If you use --partial or --inplace and you don't use --whole-file that is
exactly what it will do.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.