I still stuck with these errors
packet_write_wait: Connection to 192.168.10.43 port 22: Broken pipe
rsync: connection unexpectedly closed (534132435 bytes received so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(605)
[receiver=3.0.9]
rsync: connection
On 19/03/18 14:01, Morgan Read wrote:
Hello list
I've been running the following command, first in fc20 and then now
(since the beginning of March) in fc26:
now=$(date +"%Y%m%d-%H%M"); sudo rsync -ahuAESX -vi /home/
/run/media/readlegal/Backup/home >
Since your problem is really that your ssh connection is dropping maybe
you need more verbosity/debug on the ssh part (possibly even on both
ends). Also, if you are using --checksum don't.
On 03/25/2018 09:43 AM, Marc Roos via rsync wrote:
>
> I still stuck with these errors
>
>
You could try using an automounter, like autofs, in combination with
sshfs. It'll be slower, possibly a lot slower, but it should be more
reliable over an unreliable connection.
I've been using:
remote
Note that if you do this you are stuck with --whole-file
On 03/25/2018 04:36 PM, Dan Stromberg via rsync wrote:
> You could try using an automounter, like autofs, in combination with
> sshfs. It'll be slower, possibly a lot slower, but it should be more
> reliable over an unreliable connection.
https://bugzilla.samba.org/show_bug.cgi?id=13268
Wayne Davison changed:
What|Removed |Added
Resolution|--- |FIXED
The branch, master has been updated
via fb7a162 Prepare the repository for more development.
from d73762e Preparing for release of 3.1.3
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
commit