I have been using Syncthing for a few years, on Synology DSM, TrueNAS CORE, TrueNAS SCALE and Windows to sync 10TB+. I mostly have been very very happy with it.
Recently Syncthing on my main TrueNAS server is always crashing due to corrupt database, I have deleted the database ( index-*.db) two times now and after this it has to re-hash everything that takes a lot time on a large data set. I don’t believe this system has any RAM or hardware issues. I will memtest it in the coming week.
This all started because I wanted to mass rename some files/folders on my media, I hoped if I did it on one system the renames would carry over to the other systems without having to transfer many TB’s of data.
This process got me digging into the folders more closely and I discovered a lot of “sync-conflict” files. And also also “.tmp” files that are also “sync-conflict” files.
My current status is I have a Sync folder on two systems showing “Out of Sync” with 191GB of data that is Out of Sync. The TrueNAS system I need to delete the database again and hope I can get Syncthing to be stable again. However before I do this I am writing a script to delete all of the “.tmp” and “sync-conflict” files. The Out of Sync files are “sync-conflict” files only.
I hoped these two systems would become in sync without the third one having to be online.
So a few issues here, but my main query is about Syncthing having so many “sync-conflict” files present. These are using up 450GB+ on this on Syncthing folder.
With this kind of OS mixture, you should make sure the “ignore permissions” option is checked under each folder’s advanced settings. That might be a reason for the getting the conflict files in the first place.
You should also check the other devices for error messages on the folder. Usually the conflict files originate from one device which gets an update from a remote. The are subsequently pushed to all other devices linked for the this folder. Now if the conflict files end up with a tmp suffix and stay like that, it usually means they cannot be renamed to their final name or permissions / mod time should be applied and the system refuses to let Syncthing do that. Either way, you should have error messages on the folder or in the log stating what’s gone wrong.
And full screenshots of the folder / device sections in the GUI would help in troubleshooting.
I am mostly using Synology DSM on my storage systems.
I have been having trouble with this TrueNAS server and was thinking its time to migrate the data off of it and set it up again as with Synology DSM OS.
Anyway… Syncthing has been working ok on this server mostly this past week or so. Its a storage server I use daily. The Syncthing database corrupted again.
I finally put it on the bench and ran Memtest86… and yes the RAM in the system has gone faulty!! Omg the headache I have had because of this!
And now I have a lot of conflict “sync-conflict” files… and some new basic software I wrote to check my Syncthing folders.
The thing is I would have never discovered (or not for a long time) that the RAM was faulty if it was not for Syncthing. So thanks Syncthing… a use-case for this software that I did not know existed.
As a network drive its been working fine and hopefully it (and Syncthing) issues will be resolved now.
