4 ms·
I use syncthing and appreciate that it exists. It's way too easy to accidentally all your data, though! I've been dragging my feet migrating a hard drive from
by sgtnoodle 4y ago
I use syncthing and appreciate that it exists. It's way too easy to accidentally all your data, though!
I've been dragging my feet migrating a hard drive from my old desktop to my new one for 1.5 years. This past weekend I finally got motivated to power the old one up and wait for syncthing to give positive indication that it's in sync with my server. The reason that was even a concern of mine is that the last time I used that desktop, I spent a whole weekend cleaning up about 200 GB of renamed and duplicated "sync conflict" files that syncthing created and then synced to my server when I previously migrated hard drives. I wasn't sure if all the fixes had made it to the server yet. That required writing my own tooling to positively confirm every duplicate was bitwise identical before deleting one or the other.
The official documentation suggests I remove syncthing's metadata from the drive and then add it again on the new computer, and let it re-sync. It's a good way to check for bit-rot I guess. At least the documentation these days suggests marking one instance as read-only.
- Sakos 4y agoI've managed to delete a folder with GBs of important data because Syncthing has non-obvious ways of handling data. Thankfully, I have tons of backups of everything, so it wasn't a big deal, but since then I've been extremely paranoid when using Syncthing to make sure it doesn't happen again.
- syntheweave 4y agoI do all my work with Syncthing in send-only folders, one per machine. Which means that if I make changes across machines then I always get duplicates, but the redundancy feels natural - it's only concerning if the data size becomes absolutely huge.
- jbverschoor 4y agoSyncing is anything but elegant
- jrm4 4y agoOn one hand I haven't found it all that easy, but on the other, I think the principle of "sync is not backup" holds pretty well.