Hello, I have 2 network cards on my 2 of my computers that I am trying to transfer data on. The second network cards are specifically for transferring files between the two so I enabled jumble frames by setting the mtu to 9000. I seem to be able to connect between the two via ssh and other methods using this setting so I thought everything was working right until I tried rsync. I used the following command and got the error below: # rsync -auv -e 'ssh' root@192.168.30.20:/srv/data /srv/data Password: receiving file list ... Read from remote host 192.168.30.20: Connection reset by peer rsync: connection unexpectedly closed (8 bytes received so far) [receiver] rsync error: unexplained error (code 255) at io.c(459) [receiver=2.6.8] I'm using rsync 2.6.8 on both ends and never had this problem before until I changed the mtu. Anyone know of a way to fix this or does rsync not work with jumbo frames? Thanks, - Jake
Let me guess that you are going through a switch... does the switch support jumbo frames? Perhaps the simple ssh traffic and "other methods" does not generate any frames over your switch's capacity. Go to the mfg web site and read the spec sheet. The network layer is below rsync. rsync should be independent and should not try to be aware. Jake Conk wrote:> Hello, > > I have 2 network cards on my 2 of my computers that I am trying to > transfer data on. The second network cards are specifically for > transferring files between the two so I enabled jumble frames by > setting the mtu to 9000. I seem to be able to connect between the two > via ssh and other methods using this setting so I thought everything > was working right until I tried rsync. I used the following command > and got the error below: > > # rsync -auv -e 'ssh' root@192.168.30.20:/srv/data /srv/data > Password: > receiving file list ... Read from remote host 192.168.30.20: > Connection reset by peer > rsync: connection unexpectedly closed (8 bytes received so far) [receiver] > rsync error: unexplained error (code 255) at io.c(459) [receiver=2.6.8] > > I'm using rsync 2.6.8 on both ends and never had this problem before > until I changed the mtu. Anyone know of a way to fix this or does > rsync not work with jumbo frames? > > Thanks, > - Jake
On 10/3/07, Jake Conk <jake.conk@gmail.com> wrote:> [...] I enabled jumble frames by setting the mtu to 9000.Jumble frames! Now there's an idea to join the ranks of the April Fools' Day RFCs! :-D Matt
I think whatever your reading is probably wrong. It doesn't make sense or else like wha you said nothing will be able to communicate over jumbo frames. Jake On 10/5/07, Matt McCutchen <hashproduct+rsync@gmail.com> wrote:> On 10/5/07, Jake Conk <jake.conk@gmail.com> wrote: > > I don't get it. > > According to Wiktionary, jumbled = in disarray, mixed up. So I would > be surprised if any program managed to communicate over jumble frames. > > Matt >