I created a one-way synchronization pipeline from Windows 10 to Synology NAS. At Windows side, the Syncthing Folder is set as send-only, at NAS side it is set as receive-only. Several problems emerged.
The first synchronization resulted in directories with incorrectly set privileges at NAS side. All directories had the Delete privilege disabled (folder > Properties > Permission). On the contrary, the NAS directory corresponding to the ST Folder Path has all Read/Write privileges inherited and enabled.
Hence I set the privileges for the whole tree, now they are inherited everywhere. This resulted in that all(?) items at NAS are now marked as Locally Changed.
I believe this is also related with How to accept local changes.
- Moreover, at Windows side, I moved content of a directory somewhere else, and when realizing the mistake, I returned the files back. Now, all the moved (and returned) files and folders are marked at NAS side as Failed Items. The detail shows that “directory contains unexpected files, scheduling scan”.
I created another sync pipeline with the same result as in 1. But after fixing the privileges as in 2., the folder is “Up to Date”.