Syncthing alternatives
-
Yeah AMD's memory controllers, especially DDR5 seem to have a lot more difficulty at high speed with 4 slots filled. I used to plan upgrades around populating 2 slots and doubling if needed a few years later, instead now you really need to plan to ignore those slots if you are needing memory performance for things like gaming versus raw capacity.
Yeah, I didn't need 128GB, but as soon as I figured what's going on with the 4-DIMM config, I ordered another kit to fill what I think I'd need for the lifetime of the system.
-
Check my edit.
That is some crazy story right there. I do know for a fact that memtest needs multiple passes. But in my case the machine only has 1 stick of ram (used to have 2, one died). I will probably do a memtest overnight and get at you tomorrow.
-
Yeah, I didn't need 128GB, but as soon as I figured what's going on with the 4-DIMM config, I ordered another kit to fill what I think I'd need for the lifetime of the system.
Similar issues even with just 2 DIMMs with some XMP/EXPO profiles not working on AMD systems because of board/CPU limits. It should technically work, but for whatever reason it just can't handle it and speeds need to be dropped or the timings loosened a bit even though the RMA itself is rated for that.
Not that the higher speeds are even necessary for 90% of users outside extreme overclocking. DDR5 6000 is basically where you reach diminishing returns anyway, and that's often where that limit seems to appear.
-
That is some crazy story right there. I do know for a fact that memtest needs multiple passes. But in my case the machine only has 1 stick of ram (used to have 2, one died). I will probably do a memtest overnight and get at you tomorrow.
(used to have 2, one died)
That would make me immediately look to the RAM as the possible source or corruption. If it used to be a matched pair and one stick died, the odds of the other being on its way out are MUCH higher than normal. I would never trust that matched stick.
-
Never tried unison or resilio can check. As for seafile, that is what I had before. At some point I realized I was getting several issues with desktop mostly, and the storage was only accessible from seafile wich in my case I am not OK with. Mostly was the inconsistencies between oses
wrote on last edited by [email protected]There is a dockerized version of GoodSync, tho I've only used the windows version, so I can't really vouch for it. Might be something worth looking at. I chime in with the others here in that I use Synchthing and I've never had any issues with corrupt files, but I can understand how that would be unacceptable.
-
I could try to do that, but I simply do not have reproducible steps that are certain to make the problem happen. I am a developer myself, and I absolutely despise when someone says 'hey, something random happened the other day. I cannot say what are the steps, but it is there' just to find out in the end nothing is there, or is simply not reproducible no matter what and for reasons that I might never find out
Someone might recognise your issue though and have suggestions, even if you can't reproduce it exactly
-
Similar issues even with just 2 DIMMs with some XMP/EXPO profiles not working on AMD systems because of board/CPU limits. It should technically work, but for whatever reason it just can't handle it and speeds need to be dropped or the timings loosened a bit even though the RMA itself is rated for that.
Not that the higher speeds are even necessary for 90% of users outside extreme overclocking. DDR5 6000 is basically where you reach diminishing returns anyway, and that's often where that limit seems to appear.
Ugh. And as far as I'm reading, we're hitting limits with the connectors and interconnects so the next iteration up might require some type of CAMM interface.
-
Syncthing runs encrypted anyway.
Encrypting the connection is good, it means that no one should be able capture the data and read it - but my concern is more about the holes in the network boundary you have to create to establish the connection.
My point of view is, that's not something you want happening automatically, unless you manually configured it to do that yourself and you know exactly how it works, what it connects to and how it authenticates (and preferably have some kind of inbound/outbound traffic monitoring for that connection).
-
From what I see, kopia is for the desktop. Unless I didn't see something, it is not available for android, which is where more important to have backup in my case
Aah my bad.. I was half asleep. What I meant was use Round Sync / Syncthing to copy files to pc and then use Kopia to backup. Round Sync can do one direction copying, so source files are not corrupted.
-
Hi,
As the title suggests: what are alternatives to syncthing that are basically fire and forget, works on multiple device types, and just focuses on file syncing?
I've had over the months the weirdest problems with syncthing, and lately I noticed some of my photos got corrupted, which is an absolute no no for me. I use syncthing currently as a easy automatic backup of documents, photos and other files, between my PCs and my phones (they all send only to the server. Folders are not shared with other devices).
I am using rsync triggered by cronjobs for this task now for... well... nearly forever.
-
(used to have 2, one died)
That would make me immediately look to the RAM as the possible source or corruption. If it used to be a matched pair and one stick died, the odds of the other being on its way out are MUCH higher than normal. I would never trust that matched stick.
Finished an all nighter memtest with a total of 12 passes. All good on the ram side
-
Finished an all nighter memtest with a total of 12 passes. All good on the ram side
Crazy, thought for sure it would fail testing.
Still wouldn't trust it personally after a failed stick from a matched pair regardless of what the test says though.
-
Aah my bad.. I was half asleep. What I meant was use Round Sync / Syncthing to copy files to pc and then use Kopia to backup. Round Sync can do one direction copying, so source files are not corrupted.
That is something I can totally do after I figure out this syncthing thing. Probably will use Borg backup but same principle applies
-
That's really weird. I've been using it for mobile-desktop-server-offsite sync for many years, with transfer sizes over 15TB, over WiFi, cellular, cable, fiber. I've never seen data corruption. Conflicts, sometimes. Permission issues, sometimes. Wiping something accidentally, sometimes. It's even more weird because Syncthing performs computes hash values for the files it manages. I don't know if it performs hash validation after copying remotely but if not, it can be forced manually which would tell you what's fucked and be pulled from the source, if it still exists.
Nevermind, it verifies the result:
When a block is copied or received from another device, its SHA256 hash is computed and compared with the expected value. If it matches the block is written to a temporary copy of the file, otherwise it is discarded and Syncthing tries to find another source for the block.
According to this, if you have data corruption it can only occur between copying/moving a temporary file on your destination to another directory, or it could occur on the source itself. Both of those scenarios are a cause of concern and would likely persist with any utility. Moving or copying a file from one location to another on a sane machine should not corrupt it. If I were you I'd ensure my server doesn't eat bits. If not the storage media, it could be bit rot, or bad RAM.
Just in case everything seems fine, let me tell you what I dealt with. I had a Ryzen 5950X machine with 32GB of RAM. It worked well since inception with no signs of RAM or data corruption issues. I test every new machine with Memtest86+. At some point I migrated the storage from Ext4 on LVMRAID to ZFS. All good. Then I wrote an alarm for Prometheus to tell me if there's any issues in ZFS. A week later I get an email about a ZFS error. I check the system - says checksum errors, data has been corrected, applications unaffected, run a scrub to clear. I ran a scrub. A few more checksum errors found, all corrected, we're clean now. There was a strong solar storm around that time, probably that. A couple of weeks later I get another email. Same symptoms, same procedure. No solar storm. Shit. Memtest86+ - pass. Hm. A couple of weeks later I get another. Same thing. Memtest again - nothing. This went on for several months. Meanwhile the off-site backup sees nothing like that. While running Memtest on another machine I noticed that the test passes following the first took longer than the first, a lot longer. I thought something might be wrong with that machine. Dug into it, got into Memtest's source code and discovered that the first pass is shorter on purpose so that it quickly flags obviously bad RAM. Apparently if you want to detect less obvious issues, you have to run multiple passes. OK. Memtest the main server again, pass 1: OK, pass 2: OK, pass 3: OK, pass 4: FAIL. FUCK. Memtest each stick separately for 4 passes: OK. Memtest 2 at a time: OK. Memtest all 4: FAIL. Alright, now we know why ZFS keeps finding checksum errors. Long story short, this machine could not run this RAM in 4-DIMM config. Replaced it with another RAM that's rated to run in 4-DIMM config on that processor. No more checksum issues. If I was running the older Ext4-on-LVMRAID storage stack, I would have caught NONE of these and it would have happily corrupted files here and there. In fact it likely did and I have some corruption. Moral of the story - run many Memtest passes and use checksumming storage stack like ZFS or Btrfs. I strongly recommend ZFS since its stripe RAID works fine unlike Btrfs'es. If you don't find bad RAM, start using it today, even if you're working with a single disk and add redundancy when you can. Only after change Syncthing for something else if you still somehow get corruption without ZFS'es knowledge. And if ZFS tells you that you have checksum errors, you likely have bad hardware.
This post doesn't benefit me at all but I love how long it is.
-
Hi,
As the title suggests: what are alternatives to syncthing that are basically fire and forget, works on multiple device types, and just focuses on file syncing?
I've had over the months the weirdest problems with syncthing, and lately I noticed some of my photos got corrupted, which is an absolute no no for me. I use syncthing currently as a easy automatic backup of documents, photos and other files, between my PCs and my phones (they all send only to the server. Folders are not shared with other devices).
wrote on last edited by [email protected]Is Syncthing my ideal backup application?¶
No. Syncthing is not a great backup application because all changes to your files (modifications, deletions, etc.) will be propagated to all your devices. You can enable versioning, but we encourage you to use other tools to keep your data safe from your (or our) mistakes.
https://docs.syncthing.net/users/faq.html#is-syncthing-my-ideal-backup-application
Sync is sync. Sync is NOT backup.
-
Crazy, thought for sure it would fail testing.
Still wouldn't trust it personally after a failed stick from a matched pair regardless of what the test says though.
wrote on last edited by [email protected]Yeah. But it could be the board that burned it. But yeah, dead RAM is bad news, something is likely up. If I had data corruption and RAM didn't show errors I'd begin swapping components. If the machine is cheap and swapping components would be too expensive or impractical, I'd swap the machine for another, like a cheap second hand Dell box.
-
Finished an all nighter memtest with a total of 12 passes. All good on the ram side
wrote on last edited by [email protected]Condolences, you just switched to Ultra-Violence.
-
This post doesn't benefit me at all but I love how long it is.
wrote on last edited by [email protected]Let me tell you about diagnosing a reproducible crash on that 5950X system after swapping the RAM with verified good modules. An issue I only discovered because I decided to warm myself using Folding@home for a couple of cold days while my building was switching the central heating on.
-
Could be a bad AP.
I once had a switch with a failing power supply that would corrupt MP3 artwork when writing to the MP3. That was a weird one to track down.
That sounds like a crazy story to find out what the issue was. As I stated somewhere on the thread, ram is not the issue, and the APS are quite new (Aruba stuff that is 1 and a half year old). And the only situation I get this issues is with my phones in specific. I will probably use the smb solution stated before and see how is goes. If the thing still happens, then is hunting time
-
Yea, gotta be something odd with your setup.
Currently I have one phone (of several) thats syncing en excess of 10,000 files, some only on Wifi (with 3 access points), some wifi/cell data.
ST knows the state of a file, so a disconnect should have no effect. If you're getting corrupted files, I wonder if something else is going on which may also affect another sync tool.
Try Resilio for the same folders, see if you have the same problem (disable Syncthing of course, otherwise conflicting edits will cause file corruption).
I checked their page and I have now a personal license. I am going later to try to find out how it works, so we will see
