Marc Roos via rsync wrote:
> Hmmm, looks indeed like changing the mtu helps, strange thing is that
> with the bigger mtu sometimes I had no problems and often TB are copied
> without problems.
> Problem is I can't test the connection that much because the connection
> has been established by a
some vlan without
any hops.
But thanks for the link to the nfs-test that looks interesting!
-Original Message-
From: Dan Stromberg [mailto:drsali...@gmail.com]
Sent: donderdag 29 maart 2018 4:36
To: Marc Roos
Cc: rsync
Subject: Re: Rsync between 2 datacenters not working
If reducin
e-
> From: Kevin Korb via rsync [mailto:rsync@lists.samba.org]
> Sent: zondag 25 maart 2018 22:42
> To: rsync@lists.samba.org
> Subject: Re: Rsync between 2 datacenters not working
>
> Note that if you do this you are stuck with --whole-file
>
> On 03/25/2018 04:36 PM, Dan
: zondag 25 maart 2018 22:42
To: rsync@lists.samba.org
Subject: Re: Rsync between 2 datacenters not working
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
>
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.
>
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
-fstype=fuse,allow_other,nodev,noatime,reconnect,ServerAliveInterval=15,ServerAliveCountMax=40
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
>
> packet_write_wa
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 unexp
