more intelligence on first sync when destination folder exists


iaw4

Recommended Posts

 

there is an old rsync confusion, where adding a "/" on the directory could mean totally different things.  for rsync, one does a dry-run (-n) to make sure one has it right.   a small confusion can easily end up with gigabytes of duplicates.   for resilio sync, this is more difficult.

suggestion: on an initial synch, I would suggest three things:

  1. IF the destination folder is non-empty, collect info on how much needs to be actually transferred.  after the reconciliation calculation, confirm with the user  whether (s)he really wants to transfer move 100,000 files in 1 TB.
  2. similar to 1, give information about how many files would be added/duplicated/removed/etc.  perhaps give a few sample filenames where they would be before and after.
  3. pick a few unusual and unique filenames from the two directories, see if there is a similar file on the other volume, and if there is, most likely what the user wants to do is for these two copies to become one copy.  something else is unlikely.  (anything else that would result in two copies should request at least one confirmation.)

I know this is extra code, but it's a special and important single use case.  because all that changes is an extra warning panel (if a preference is checked), and the underlying behavior of resilio is not changed, this should be doable.

regards,

/iaw

 

Link to post
Share on other sites
  • 10 months later...
  • GreatMarko changed the title to more intelligence on first sync when destination folder exists

Archived

This topic is now archived and is closed to further replies.