Issues with file/folder moved or deleted on Initiator

[Julien76]

Hi,

I'm trying to set-up osync to synchronise two hard drives locally.

When running dry-test, I have the following issues:

1. On INITIATOR, I move a folder name FOLDER_A (just for the example) to a different location.

2. I run osync as follow: osync.sh ~/.config/osync/sync.conf --dry --summary

3. In the summary output, osync wants to copy FOLDER_A from the TARGET to the INITIATOR, instead of deleting FOLDER_A on TARGET.

4. On INITIATOR, I move a delete name FOLDER_A.

5. I run osync as follow: osync.sh ~/.config/osync/sync.conf --dry --summary

6. In the summary output, osync wants to copy FOLDER_A from the TARGET to the INITIATOR, instead of deleting FOLDER_A on TARGET.

My configuration is as follow:
Linux julien-manjaro-pc 4.14.30-1-MANJARO #1 SMP PREEMPT Sun Mar 25 19:47:20 UTC 2018 x86_64 GNU/Linux

Osync: osync 1.2 2017032101

My config file is the default where I just change the INITIATOR_SYNC_DIR and TARGET_SYNC_DIR, and added to the exlcude_file list .Trash-*

Is this a bug? Am I doing wrong something?

Thanks in advance for your help.

[deajan]

Hello,

Sorry for the delayed answer.
As a matter of fact, osync is a stateful sync system, meaning you have to run it once before it can detect deletions (which it does by comparing file lists with a previous run).
Running with --dry won't actually update the state files since it won't alter anything, and is supposed to be run once you have done an initial sync in order to check what changes are next.

[Julien76]

Hi,
Thanks for the answer.
I will run a one-way sync with rsync first to be sure the two drives start with the same content (cause there are too much data to copy on both side, while only the state of the INITIATOR matters for me on the first run).

[deajan]

Keeping the idea for next version.

[deajan]

Added --initialize option in 7621f3e