https://bugzilla.samba.org/show_bug.cgi?id=6719
Summary: I/O error protection is broken w/ protocol 30 and
incremental recursion
Product: rsync
Version: 3.0.6
Platform: All
OS/Version: All
Status: NEW
Severity: critical
Priority: P3
Component: core
AssignedTo: way...@samba.org
ReportedBy: m...@mattmccutchen.net
QAContact: rsync...@samba.org
See http://lists.samba.org/archive/rsync/2009-September/023892.html . IIUC,
the feature that disables deletion upon an I/O error is mostly non-functional
with protocol 30, incremental recursion, and --delete-during. That could lead
to a catastrophic loss of destination files, which the feature was intended to
prevent.
One safe behavior for a sender that gets an I/O error and is unable to report
it reliably to the receiving side would be to exit immediately with a message
explaining the issue. That way, users with rsync 3.0.* (the current stable
branch) can still use incremental recursion safely and then switch to a
different approach if they frequently get I/O errors.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
