Am I reading correctly that SyncThing cannot detect changes that were made via an SMB user? E.g. I can’t use Syncthing to continuously backup a NAS where users are modifying or creating files via SMB.
I did a quick test/demo locally and even with a manual “Rescan” button press a new text file created via Explorer was detected but not a new file created by a \UNC\path session.
When Syncthing is accessing a folder over SMB it needs to rely on periodic scans instead of change notifications. Changes still get picked up, but with slightly higher latency.
If you’re running Syncthing directly on the NAS this does not apply. You may be seeing a permission problem of some kind.
It must have been a permission issue. It’s been running smoothly since on Synology, Docker and Windows Server with users predominantly modifying over SMB.