samba-bugs at samba.org
2013-Aug-12  15:58 UTC
[Bug 10081] New: Multiple rsync instances conflict
https://bugzilla.samba.org/show_bug.cgi?id=10081
           Summary: Multiple rsync instances conflict
           Product: rsync
           Version: 3.1.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P5
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: xaionaro at gmail.com
         QAContact: rsync-qa at samba.org
When running multiple instances of rsync with "--backup" option on
same file
(for example in case of intersecting include-files), few of them can exit with
exitcode "23".
It happens due to nonatomicity of robust_unlink()&do_open() operation in
copy_file(). While one of instances is proceeding between robust_unlink() and
do_open(), another instance can run do_open(). So the first instance will fail
on do_open() due to flag "O_EXCL".
I suggest to remove the flag "O_EXCL" if copy_file() is called from
make_backup() function.
Overwriting of "backuped" file is fine behavior, so why not to permit
it even
for this special case?
-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
samba-bugs at samba.org
2014-Jan-02  11:01 UTC
[Bug 10081] Multiple rsync instances conflict
https://bugzilla.samba.org/show_bug.cgi?id=10081 --- Comment #1 from Dmitry Yu Okunev <xaionaro at gmail.com> 2014-01-02 11:01:10 UTC --- I can write a patch. Is this required? I can make my modification to be optional, if this required. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2015-Feb-11  10:48 UTC
[Bug 10081] Multiple rsync instances conflict
https://bugzilla.samba.org/show_bug.cgi?id=10081 --- Comment #2 from devurandom at gmx.net --- I assume this is not being considered, because the backup needs to be restored in case the new file is corrupted? So overwriting it would be bad? -- You are receiving this mail because: You are the QA Contact for the bug.
Possibly Parallel Threads
- new option suggestion '--backup-only'
- [patch] Make robust_rename() handle EXDEV.
- [Bug 10356] New: Include rsync-no-vanished support script
- [Bug 10681] New: Add an option to delete non-existent files in --files-from
- [PATCH] Add --preserve-atime switch to rsync