TL;DR - If shared folder has to be on a network mount use NFS over CIFS to avoid issues.
So inititally, when I first fired up Syncthing I added 3 nodes (laptop, desktop, and NAS). However, my NAS kept on throwing out errors like in the link above. All it said was “Drive readdirent no such file or directory” and pretty much nothing else. Other issues included:
- Rescan kept on failling
- Files were randomly being deleted from the NAS
- Files would sometime would reappear hours later
No issues with only the desktop and laptop online. Just the NAS causing all the issues. The initial sync goes without a hitch, and about a few hours later that’s when the issues start to come up. After reading through some old threads, it seems like the location of my shared folder was the issue. It sat on a CIFS mount. The fix turned out to be, to turn it into an NFS mount instead. Not sure if this is expected behaviour because it’s not mentioned in the documentation. Is CIFS just bad?
I was reading in other threads where it said that SAMBA/CIFS shouldn’t be an issue. If I’m doing something wrong though it would be great to hear suggestions. I’ll explain my setup the best I can below. I thought I’d share in case anyone else runs into this situation.
- Using Openmediavault with Docker.
- Using the linuxserver/syncthing image (1.12.0).
- NAS (1) mounted a shared folder of another NAS (2) for syncthing.
- Syncthing config files stayed on NAS (1).
After switching the mount from CIFS to NFS, all seems to be working fine now.