I’m having issues with constant conflicts on a dual-boot system, hoping someone might have an idea of how they could be alleviated. Here’s the setup:
Syncthing is syncing a folder between my PC and a NAS (send and receive at both ends). The PC is a dual boot system (Windows+Linux), so locally, the folder is actually pointed to by two installations of Syncthing, though obviously only one of them would be active at a time (depending on which OS is booted).
The issue is that if I edit a file, then reboot to the other OS without waiting for it to completely upload to the NAS, then continue working in that file from the 2nd OS, I get conflicts. Note that the file is never touched remotely (on the NAS) - it’s only being edited on the shared local partion. As an example, if I’m on Linux, edit db.ctb, reboot to Windows, continue working in db.ctb, I will see conflicts named i.e. db.sync-conflict-20220323-200523-XXXXXXX.ctb, where XXXXXXX is the device ID of Windows (the OS that I booted into).
What I’d like to do is be able to keep this folder synced between my NAS & local PC (whether I happen to be booted to Linux or Windows), but without having constant conflicts whenever I need to reboot. I should mention that I do need the NAS<->PC syncs to be bi-directional, as there are there are actually other PCs that also sync via the NAS - however for simplicity when debugging these conflicts, I have all other PCs powered: only two clients are online, the NAS and whichever local OS is booted (either Windows or Linux).
Thanks in advance.
4 posts - 2 participants