I’m starting to experimenting with Syncthing and experienced below issue.
Computer A = “Comp-izba”, Windows 10, Syncthing 1.14.0
Computer B = “Comp-obyvacka”, Windows 10, Syncthing 1.14.0
Computer A is showing:
Computer B is showing:
- Folders are perfectly Synced although computer B is saying they are still syncing.
- Both folders are Send & Receive, no file versioning, no ignore patterns. Although this was not initial setup, details below.
- Folder contains very large files, some over 6-7 GiB. Maybe this is relevant.
- There were no power outages, RAM or other HW issues.
- On both sides, Syncthing service was shutdown and started and even entire computer restarted multiple times.
Are folders really synced?
Yes, they are. Initially Computer A had more data and I wanted to use Syncthing to sync missing data to Computer B. Initially I shared “Trainings” folder on Computer A as Send Only. When prompted on Computer B, I left default share setting (Send & Receive), but changed versioning to Trash Can File Versioning. At that point it started to sync, although both computers were showing different amount to be synced on right side. Maybe should I had give Computer A more time to calculate the folder before I accepted the prompt and created the share on computer B?
When it synced I think left side changed to Up to Date but both sides were still showing Syncing status on right side which was stuck. Sorry didn’t make screenshot at that time. At this point it was strange and I think I even did Rescan all, but it didn’t change anything. Then I decided to change Computer A share type to Send & Receive - it immediately changed the status of remote device on right side to Up to Date.
So Computer A was fixed and as expected, but Computer B is stuck. I changed File versioning to No File Versioning - no help.
So I checked amount of data, number of folders and files is exactly same on both sides. I though noticed that although Modify time on files is the same, Creation time is not. So I used Windows command utility Robocopy with /MIR and few other parameters to mirror source to destination. It reported files as modified in source, but didn’t copy any (skipped all folders and files). It did make sense, because if modification time is the same, there is no reason to copy anything over. However, there is also /TIMFIX parameter, which will change timestamps, and apparently also creation time timestamps. So I tried with /TIMFIX and now even creation timestamp as well as modify timestamp are the same. Even another attempt with /MIR now says that all files are the same.
So indeed, if Robocopy says files are same (in sync), they must be.
Anything else I was concerned about?
Yes, permissions. I initially tested SyncThing with elevated permissions, and on computer B even with different user account. On computer B I later changed the user under which Syncthing is running, so I had to shutdown Syncthing and move its data in C:\Users\original_user\AppData\Local\Syncthing to C:\Users\current_user\AppData\Local\Syncthing . Also moved the Sync folder of Default Folder to new location and changed its location in Advanced Configuration, but this is not relevant I assume.
I am now running Syncthing in Task Scheduler as per User Guide on user logon. Although in reality Syncthing synced the folders, I was concerned user under which scheduled task is running don’t have permissions to the folder. Indeed, that user didn’t have permissions, but Authenticated Users group did have Modify, so the user had effective permissions. Anyway I added also the user to permissions with Full Control, but no help.
I have User Account Control (UAC) enabled on both computers so I also changed the scheduled task to run with elevated permissions (user under which it is running is admin but will not use admin privilleges until you tell it to use elevated privilleges), this didn’t help either.
So what now?
Folders are synced, permissions are good. I don’t see anything suspicious in logs, both computers are on same subnet. I know I could probably start from scratch or reset the DB, but would be good if there is other mean to resolve this. Maybe there is something on my end that I did not consider yet. I noticed few more people reporting this kind of issue, but there is always some other variable, so I decided to open new topic.
Do I have any idea what I can try? Or any more information I could provide to help?