I recently shared a folder to a new laptop dual-booting Windows and Linux, and when it is online in Linux every change I make on another device causes a sync conflict.
The conflict file is just the previous version of the file before I saved, and the file name indicates it was modified by where I intended to modify the file. (That is, when I modify the file on my desktop, I get a sync conflict file with my desktop’s ID.)
This is what the recent changes menu on my laptop looks like when I updated a markdown file on desktop-12. bluefin is my laptop.
Both Windows and Linux run Syncthing. They have their own individual installs and configurations, but they both sync the same folder on Windows’ C drive. My only idea is that it’s due to NTFS somehow, but from what I’ve read that should just cause performance issues?
With dual booting, the best and safest way to use Syncthing is to set up a portable-type installation, where the database and config are shared between the two, and the folders use relative paths (with / slashes that are supported by Syncthing in Windows as well). You should also makes sure that Syncthing binaries are exactly the same version, with automatic upgrades disabled.
We’ve had this type of installation discussed quite a few times, so I think you could also find some useful information if you try searching the forum for “dual boot” .
I’ve since abandoned dual-booting for an unrelated reason, and now I’m only running Linux. From what I can tell I no longer have this issue. I’m still monitoring, though.
I don’t think dual-booting was an issue as I primarily ran Linux anyways, but I could be wrong about that. What primarily changed on Linux is that Syncthing is no longer syncing a folder from an NTFS drive that Windows was installed on. So if I had to guess, that was probably the issue somehow?
.