Wi-Fi Interference vs. Daemon Drama: Why rsync Fails and Which Sync Tool Actually Works
Most contributors agree that rsync failures during unstable remote sync sessions trace back to poor Wi-Fi signal, multicast spam, and channel interference, not version protocol mismatches.
The main software fight pits Synchi against Syncthing. Supporters of Synchi, like jak0b, champion its 'on-demand' SSH methodology for explicit, user-approved conflict resolution. Conversely, the environment is split on the technical failures: JasonDJ demands users check for multicast sources, while just_another_person insists filesystem corruption is the culprit for verification errors.
The consensus points to network hygiene being the immediate fix for connectivity hiccups. For file syncing, the community favors Synchi's controlled, SSH-based transfer process, while experts like jak0b point to the simplicity of rsync for one-way mirroring due to its lack of memory between runs.
Key Points
WiFi instability is caused by interference, not protocol errors.
JasonDJ stated high packet loss is almost always due to interference or weak signal, suggesting narrower WiFi channels over wider, congested ones.
Synchi's on-demand, SSH approach is superior for conflict management.
jak0b argues Synchi prevents unexpected halts because it forces users to explicitly approve every data change via scan.
Syncthing's background daemon requirement is a major drawback.
The core controversy pits Syncthing’s need for 'always-on daemons' against Synchi's pull-on-demand model.
rsync is best used strictly for one-way backups.
jak0b asserts rsync's 'no memory between runs' is a feature, not a bug, for simple mirroring tasks.
Filesystem integrity issues must be checked first for verification failures.
just_another_person argued that file verification errors signal an underlying filesystem problem on the source or destination.
Using 40MHz WiFi channels provides better Signal-to-Noise Ratio.
JasonDJ provided the technical insight that narrower channels are more reliable than congested 80MHz or 160MHz bands.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.