similar to: Consistent crashes when syncing large file, possible bug?

Hi, I'm getting the following error occasional and can't find out why; 05/14/2011 09:28:51 rsyncing /dbtmp to /dbtmp.new (1st pass) .... rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: write failed on "/dbtmp.new/file.dmp": File too large (27) rsync error: error in file IO (code 11) at receiver.c(258) [receiver=2.6.9] rsync: connection

rsyncing a tree of perhaps 30M files, getting this: rsync: hlink.c:126: match_gnums: Assertion `gnum >= hlink_flist->ndx_start' failed. then a bit more output and

Hi, I receive this error when rsyncing. I suspect this is because of network problems. But the 'Invalid argument' and 'phase unknown' makes it very unobvious. ... packages/scribus/scribus-1.2.3-0.rf.src.rpm Read from remote host rsync.sw.be: Invalid argument rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown" [sender]: Broken pipe (32) rsync:

Hello I came about the following phenomeon when the server ( dell poweredge 2650 ) is rsyncing to the same and remote server. the connection was close and copying the file didn't finish yet. Network Topology: Dell2650 ----L2SW---L3SW---Dell2650 L2SW: Procurve4108gl L3SW: BigIron15000 when the unexpected failed come about, the ping of end-to-end is no problem, and telnet is O.K when I look

Hello, i use rsync from Windows to rsync on Linux via ssh and get IO Errors and connection unexpectedly closed errors on almost every sync run. Can anybody give me some hints on how to track down the problem? thx, Chris 2008/10/11 09:41:04 [13744] rsync to backup// from UNKNOWN (w.x.y.z) 2008/10/11 09:41:04 [13744] receiving file list 2008/10/11 09:42:48 [13744] IO error encountered -- skipping

If one enables e.g. jumbo frames without mergeable buffers, packets won't fit in 1500 byte buffers we use. Switch to big packet mode instead. TODO: make sizing more exact, possibly extend small packet mode to use larger pages. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/net/virtio_net.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git

If one enables e.g. jumbo frames without mergeable buffers, packets won't fit in 1500 byte buffers we use. Switch to big packet mode instead. TODO: make sizing more exact, possibly extend small packet mode to use larger pages. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/net/virtio_net.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git

Hi, i installed rsync 3.0 on a Sun Solaris 10 Sparc Server and tried to Backup the Server via BackupPC the complete rsync command from the backup server is this: /usr/bin/ssh -q -x -l root IP /usr/bin/rsync --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --checksum-seed=32761 --log-file=/var/log/rsync.log --ignore-times . / in the log on

I'm seeing an error that says there is a broken pipe, but the rsync command is local to one machine: /usr/bin/rsync -rltH --stats -D --delete --numeric-ids --whole-file /data/dir /backup/suse1/suse1-data-dir/ >/tmp/rsync-out 2>&1 The complete contents of the rsync-out file are: rsync: writefd_unbuffered failed to write 88 bytes [receiver]: Broken pipe (32) rsync error: error in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to sync a mandrakelinux tree (~120GB) but it bombs out after a while with this error: rsync: connection unexpectedly closed (289336107 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown": Broken pipe rsync error:

Yes, I get more than 30MB/s performance. The benchmark I use (NetBench) is essentially CPU bound, such that a faster processor = faster performance. With a very fast hardware config (dual 3.2GHz processors), I've been able to hit around 100MB/s. Changing the RAM or other attributes does not buy me much, it seems that processor power is the bottleneck (at least in my case). When doing your

Hi, Anyone else noticing any TCP Stack requests for information under a useraccount with mild to moderate TCP activity on HTTP and other sorts of ports returns zero results back unless you are root. [site@Eden ~]$ netstat -i reports netstat: kvm not available: /dev/mem: Permission denied ifnet: symbol not defined [site@Eden ~]$ netstat -an [site@Eden ~]$ netstat -m 377/823/1200 mbufs in use

Hi, I am trying to optimize my gigabit network. I have two Intel 1000 MT Gigabit Server Adapters, which support Jumbo Frames -- as well as a Switch that supports Jumbo Frames. However, I am observing some strange behavior in my file transfers from Windows XP to Linux and I am wondering if it has anything to do with the way the Samba variables are set on my Linux box? The "strange

After successfully getting higher MTU to work on my Realtek NICs, I started testing the impact of higher MTU on file transfers using NFS exported ramdisk to ramdisk. The results were unexpected. The higher the MTU on the sending NIC, the lower the file transfer speed. I tested by using time cp to copy a 1GB file (In case compression might affect the results, so I dd the test file from the CentOS

I am running jungledisk and this is my script: #!/bin/sh ### Backs up office data to Jungledisk using rsync LOGFILE=/var/log/backup-jd.log ## Start in rc.local or here #/usr/local/bin/jungledisk mount /mnt/s3 echo "`date +"%F %R"`: Start backup-jd" >> $LOGFILE rsync -r --inplace --size-only --bwlimit=50 /home/shares/allusers/127 /mnt/s3 echo "`date +"%F

We are utilizing the xen hypervisor on nexenta with ISCSI as our method of communication with the guests (currently ubuntu but could be moving to centos). Obviously jumbo packet support would be nice to have. The last time I see that on the xen roadmap http://wiki.xensource.com/xenwiki/XenRoadMap . Is there a canonical place that spells out if jumbo frames are now supported or still on the

On Fri, January 23, 2015 12:54 pm, Patrick Flaherty wrote: >> >> I do have two centos 6.6 servers. With a "performance optimized" rsync I >> get an speed of 15 - 20 MB/s >> >> The options I use are: >> >> rsync -aHAXxv --numeric-ids --progress -e "ssh -T -c arcfour -o >> Compression=no -x" >> >> If I copy files by smb

Hi, I'm using rsync to backup my data from my Linux machine (SUSE10.1) and Windows (XP) I've mounted a windows share on my linux and I'm trying now to copy files to the windows with rsync. The windows share is a NTFS filesystem It's all working except I have a error on large files. This is the command that I'm trying: rsync -a --no-o --delete

> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: >> I have seen this error in many postings, but the solutions seem not to >> apply in this case. This error happens during a small file transfer >> (gif image) and after 75% of a 165G rsync job (the building file list >> portion is complete.) Most solutions I saw were related to not having >>

https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com