[Bug 11075] New: Shouldn't --inplace fail immediately if it can't make files?

samba-bugs at samba.org samba-bugs at samba.org
Mon Jan 26 16:06:45 MST 2015


            Bug ID: 11075
           Summary: Shouldn't --inplace fail immediately if it can't make
           Product: rsync
           Version: 3.1.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: rlpowell at digitalkingdom.org
        QA Contact: rsync-qa at samba.org

20GiB file transfer with --inplace fails, consistently, *after* the transfer is

rlpowell at ip-10-0-1-16> rsync -aPv --inplace
sending incremental file list
 20,465,505,293 100%   60.10MB/s    0:05:24 (xfr#1, to-chk=0/1)
rsync: open "/data/cytobank/acs_dump_70_immuneatlas.acs" failed: Permission
denied (13)

sent 20,470,501,873 bytes  received 127 bytes  62,889,407.07 bytes/sec
total size is 20,465,505,293  speedup is 1.00
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1165) [sender=3.1.0]
rlpowell at ip-10-0-1-16> 

The file it's saying it can't open doesn't exist at all, and rsync can't, in
fact, create a file there.

So what was it doing for that 5 minutes?  Where did the 20GiB of data *go*?

I would expect --inplace to immediately try to make the file, and immediately

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

More information about the rsync mailing list