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

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

            Bug ID: 11075
           Summary: Shouldn't --inplace fail immediately if it can't
make
                    files?
           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
complete:

rlpowell at ip-10-0-1-16> rsync -aPv --inplace
~/scratch/acs_dump_70_immuneatlas.acs
10.0.11.249:/data/cytobank/acs_dump_70_immuneatlas.acs
sending incremental file list
acs_dump_70_immuneatlas.acs
 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
fail.

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

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

--- Comment #1 from Robin Powell <rlpowell at digitalkingdom.org> ---
Apparently it's not just --inplace??

rlpowell at flowcytech01> rsync -aPv
/data/cytobank/Data/experiments/1/1053/experiment_11053/attachments/attachment_24023_RightCells150Clusters5%Downsampling.zip
shell01:/var/www/special/attachment_24023_RightCells150Clusters5%Downsampling.zip
rlpowell at shell01's password:
sending incremental file list
attachment_24023_RightCells150Clusters5%Downsampling.zip
 18455631835 100%    2.43MB/s    2:00:36 (xfer#1, to-check=0/1)
rsync: mkstemp
"/var/www/special/.attachment_24023_RightCells150Clusters5%Downsampling.zip.jCvdjG"
failed: Permission denied (13)

sent 18457884862 bytes  received 31 bytes  2548551.59 bytes/sec
total size is 18455631835  speedup is 1.00
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1039) [sender=3.0.6]

So after *two hours* it finally noticed that it *wasn't writing to disk*??

How does that work?  That seems *really* bad!  I don't think rsync used to
work
like this??

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