Bug 11671 - --files-from= with nonexistant files and --delete-missing-args complains about vanished source files
Summary: --files-from= with nonexistant files and --delete-missing-args complains abou...
Status: NEW
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.1.1
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-13 18:23 UTC by Vegard Nossum
Modified: 2016-01-13 18:23 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vegard Nossum 2016-01-13 18:23:13 UTC
Problem:

rsync seems to indicate that files have disappeared during the transfer when this is not the case.

Steps to reproduce:

1. Create files.txt with "foo/bar". (Make sure "foo/" doesn't exist.)

2. Run: rsync --delete-missing-args -v --files-from=files.txt . remote-host:

Output:

building file list ... 
file has vanished: "/home/vegard/foo"
done
default_perms_for_dir: sys_acl_get_file(foo, ACL_TYPE_DEFAULT): No such file or directory, falling back on umask

sent 30 bytes  received 129 bytes  45.43 bytes/sec
total size is 0  speedup is 0.00
rsync warning: some files vanished before they could be transferred (code 24) at main.c(1183) [sender=3.1.0]

Expected behaviour:

With --delete-missing-args I would expect nonexistant files (and files in nonexistant directories) to be deleted on the remote host without any warnings or error codes.

Workaround:

Check for exit code 24 and ignore it. (But this has the drawback of potentially ignoring warnings about files which really did disappear after rsync had been started.)