I am experiencing a problem essentially identical to this thread. There was no real resolution there, except to suggest syncthing might have been the wrong tool.
This is on the same ARM7 device I talked about earlier that I had been having database corruption issues with. That problem was solved, but with a very large folder synchronized I started seeing large numbers of “locally changed items” appearing. The folder has 15k items taking 96GiB of space. I have synchronized it several times, each time there are about 30% of the files that later show as locally modified.
Originator is Windows 10, with ST version 1.13.1. Receiver is Linux ARM7 with ST version 1.11.1. Checking ignore permissions on sender and receiver did not have any significant effect.
This is on a customer’s site and my time was limited today, so I have not yet investigated in depth. On one file, though, I verified that the md5sum checksum on both sender and receiver was the same, as were modification and access timestamps the same (to the second). Creation timestamps were not the same, but they do not appear to be the same for any files that ST sends. What else could ST be using to determine if the files were changed? Is there a way to get ST to tell you why it has decided a file has been changed?