rsync problems (rsyncing many files) after NV update

[zet]

Hi,

after the last update to RAIDiator 3.00c1.0 i have massive problems rsync'ing from my WinXP laptop to the NV. I'm not sure what my old RAIDiator version was, i only know it was 3.x.

The problems starts when syncing more than (about) 40000 files, and results in a infinite hang on the client side (the client does not bring up any error message) and a strange rsynd log entry "writefd_unbuffered failed to write 4 bytes" on the server side (see below).

I upgraded from 256MB (first test set below) to 1GB (second test set below), but i saw no improvement.

Help! It worked! Give me my rsync back

Bye,

Jürgen


first test set
==============
Both test sets use a Windows XP/cygwin client:

Code: Select all

rsync --version
rsync  version 2.6.6  protocol version 29
Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
              inplace, no IPv6, 64-bit system inums, 64-bit internal inums


This is the client command line:

Code: Select all

$ rsync --progress -a --delete --delete-excluded --exclude _old_hdd/ --exclude "System Volume Information/" --exclude RECYCLER/ /cygdrive/e/ backup@space.franken.de::backup/mucn0582.e


This is the server log:
Jan 7 17:45:02 space kernel: RAIDiator version 3.00c1.0 built Wed Nov 29 15:20:42 PST 2006
[...]
Jan 7 17:45:34 space rsyncd[955]: rsyncd version 2.6.8 starting, listening on port 873
[...]
Jan 7 19:45:27 space rsyncd[4085]: connect from mucn0582 (192.168.178.28)
Jan 7 19:45:27 space rsyncd[4085]: rsync to backup/mucn0582.e from backup@mucn0582 (192.168.178.28)
Jan 7 19:55:49 space rsyncd[4085]: Projekte/LogistikBus/
[...]
Jan 7 20:11:42 space rsyncd[4085]: rsync: writefd_unbuffered failed to write 4 bytes [generator]: Connection timed out (60)
Jan 7 20:11:42 space rsyncd[4085]: rsync error: error in rsync protocol data stream (code 12) at io.c(1119) [generator=2.6.8]


second test set
==============
Next try, same client, now with 1GB Memory on the NV.

This is the client command line:

Code: Select all

$ rsync --progress -a --delete /cygdrive/c/jzeller/ backup@space.franken.de::backup/mucn0582.c/jzeller
building file list ...
81840 files to consider


This is the server log:
Jan 8 20:09:08 space rsyncd[1484]: connect from mucn0582 (192.168.178.28)
Jan 8 20:09:08 space rsyncd[1484]: rsync to backup/mucn0582.c/jzeller from backup@mucn0582 (192.168.178.28)
Jan 8 20:11:56 space kernel: chn=2, statu/LP_S=0x(d0/d050)29, 8
Jan 8 20:11:56 space kernel: chn=0, statu/LP_S=0x(d0/d050)29, 8
Jan 8 20:12:39 space kernel: chn=0, statu/LP_S=0x(d0/d050)29, 8
Jan 8 20:13:09 space kernel: chn=0, statu/LP_S=0x(d0/d050)29, 8
Jan 8 20:14:14 space rsyncd[1484]: ./
Jan 8 20:14:14 space rsyncd[1484]: Meine Shapes/
Jan 8 20:14:14 space rsyncd[1484]: Meine Shapes/_private/
Jan 8 20:14:14 space rsyncd[1484]: TimeSheets/
Jan 8 20:29:59 space rsyncd[1484]: rsync: read error: Connection timed out (60)
Jan 8 20:29:59 space rsyncd[1484]: rsync error: error in rsync protocol data stream (code 12) at io.c(614) [receiver=2.6.8]
Jan 8 20:29:59 space rsyncd[1484]: rsync: connection unexpectedly closed (1809940 bytes received so far) [generator]
Jan 8 20:29:59 space rsyncd[1484]: rsync error: error in rsync protocol data stream (code 12) at io.c(463) [generator=2.6.8]

[ewok]

A couple of suggestions:

Try updating the firmware on the NAS and the rsync on your Windows PC to the latest versions.

Try setting the MTU on your router or the NAS to 1492.

Try a similar rsync from a computer on the same local network as the NAS as a test.

[zet]

[...]
Try setting the MTU on your router or the NAS to 1492.
[...]

Using the above hint i found the solution: the Windows client had a MTU of 1300
I changed the MTU on Windows as well on the NV to 1492 Byte, and now everything works (again).

Thanks ewok!

Bye,

Jürgen