I know I am bumping an old thread, but this issue still exists, because I am still dealing with it. Here is a real live example:
Master Folder (FreeBSD)
ls -lah: -rwxrwxr-x 1 syncthing wheel 701M 13 Sep 14:01 .../DAT/SOME_INFO_2OF2_/SOME_INFO_2OF2_.wav
ls -la: -rwxrwxr-x 1 syncthing wheel 734816588 13 Sep 14:01 .../DAT/SOME_INFO_2OF2_/SOME_INFO_2OF2_.wav
sha1: dcbceffc399f13244e546e4f988459d08654321a
Remote Folder (Synology NAS)
ls -lah -rwxrwxr-x 1 someuser users 700.8M Sep 13 14:01 .../DAT/SOME_INFO_2OF2_/SOME_INFO_2OF2_.wav
ls -la: -rwxrwxr-x 1 someuser users 734816588 Sep 13 14:01 .../DAT/SOME_INFO_2OF2_/SOME_INFO_2OF2_.wav
sha1: dcbceffc399f13244e546e4f988459d08654321a
So from the above, we see that the files have the same date, and the same size, and the same SHA1 hash. So, they are the same, but the file in the master folder shows as Out Of Sync. If I click Override Changes, then it will scan, then say it is syncing for a while (but there will be no traffic) and then it will go back to Out Of Sync again.
I guess the main question is: how to remedy this?
Second, where would one look in the source code to find the logic that is determining if a file is out of sync?
Note: I have checked to ignore permissions.