DO NOT REPLY [Bug 2094] Keep the last-sync time for better two-way synchronization

samba-bugs at samba-bugs at
Wed Jul 14 05:16:17 MDT 2010

------- Comment #5 from baya at  2010-07-14 06:16 CST -------
(In reply to comment #4)
> Created an attachment (id=5844)
 --> ( [details]
> Original design document
> The link in comment #0 is long since broken.  For reference, I'm attaching the
> design document that was previously there.

Thank you, Matt, it is just more than my proposal ))) 
To the purpose: 
1) the main point is that the last-sync-time===check-point must be created
BEFORE the synchronization process. So the deletion during the update will be
synchronized next time. In other cases we will have "mysteriously coming back"
deletions (that occur during update).
2) --smart-orphans option is ambiguous and even dangerous:
 a) last-sync-time is equal check-point + dry-run
 b) last-sync-time + smart-orphans is equal check-point
VERY IMPORTANT NOTE: never increase the check-point value during any dry-runs,
never increase check-point value if synchronization is not finished without
errors - many new files will be deleted instead of being added. For the details
look at bash wrapper attached to bug 7565.

Also see notes at my PS for avoiding running rcync twice. In my situation
updating with small changes takes 3 - 5 minutes for 300MB. And this is just a
testcase, I'm going to mirror ~10G.

Additional check must be added before moving tmp file to the original position,
because the file at the original position can be updated or deleted during the
long receiving, so it will be newer than received or not needed already.

By the way, at first run check_point can be 0 (zero), which means that no
deletions occur. Just no-exists files will be added to another side.

Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the rsync mailing list