The thumb files might be generated by the NAS OS itself, so they get generated under a different user. Syncthing does not sync ownership.
Also, your NAS might not support chmod and only support ACLs which would prevent any permissions modifications. There is an ignore permissions option under the folder for this type of situations.
Nope, never. That explains your problem: The out of sync files canât be modified due to permission problems. As Audrius said, you can use ignore permissions or you can investigate the files from the log and solve the actual permission issue.
These files should however result in a failed items entry in the web UI. When you restart the folder, does no failed items row show up for this folder?
Syncing state can only happen within the puller loop, which means this is where we are at. Syncthing state doesnât last long in case of errors.
New puller loop tries 3 times, if changed is non zero, and then emits errors.
How do failed files affect âchangedâ variable in puller iteration?
I assume it doesnât and we exit after the first iteration, exiting the loop and not emitting the errors event?
Failed items do still increase changed, it essential means to be changed not has been successfully changed. However I agree I am confused now that you bring this up: During syncing errors are cleared in the web UI as at the end of syncing a new list of failed items will be incoming (or not). So does the folder in this case ever come out of the syncing state (it shouldâŚ)?
@marky_uk Do you have any log entries containing âPausing puller forâ for that folder?
So, setting âignore permissionsâ on both sides has solved the problem in entirety, and very quickly indeed. I think a rescan occurred on both, and I was then told all items are in sync! See here - https://i.imgur.com/4yvqNT6.png
Can I help any more in debugging this issue, by supplying logs directly to either of you, etc?
Iâm happy itâs now working - just to reiterate my setup is a Windows 10 PC at one side, and Synology NAS drive at the other
Glad it works. It is still unclear to me why you didât get a list of failed items after pausing and resuming the folder. If you still have access to the old logs, I would still be interested in whether there is/are lines(s) containing âPausing puller forâ after pausing and resuming the folder.