similar to: [Bug 1457] New: writefd_unbuffered failed to write

https://bugzilla.samba.org/show_bug.cgi?id=1457 ------- Additional Comments From mwang@unixlabplus.com 2004-06-13 12:05 ------- The same problem is duplicated on AIX 5.2 with current patch level 02. It appears that the problem occurs for large files. In the test shown below, it is 4.6GB. This happens for rsync 2.5.4 using the IBM build:

Hi, on HPUX 11i with ANSI/C compiler with largefile option. below rsync is on local file system. # rsync -av /prod1/* /prod1n/ building file list ... done DW/ DW/DATA/ DW/DATA/DWCOF02.DAT rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) rsync: writefd_unbuffered failed to write 69

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From wejn@box.cz 2005-08-24 05:19 ------- Strange, got this error with 2.5.7 when the destination "module" was read-only. 2.6.6 prints user-friendly info that the module is not writeable. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because:

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From maarten@xolphin.nl 2004-12-01 17:59 ------- Created an attachment (id=817) --> (https://bugzilla.samba.org/attachment.cgi?id=817&action=view) Debug information on 'other' side -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because:

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #14 from aim1@westnet.com.au 2006-02-24 08:39 MST ------- I also had the same problem ocurring randomly on large file transfers between an IDE disk and a disk attached via USB2.0 using RedHat FC4 and rsync version 2.6.4 protocol version 29. Error messages are: "rsync: writefd_unbuffered failed to write 4 bytes: phase

I am using Rsync 2.6.3 , and have tried rsync 2.6.2 also. I am attempting to push about 990G from one machine to another. Whenever I do this, it processes about 1/3 the way through and I receive the following error during the transfer, and it stops. Could this be a problem with it running as a cron job? The command I am using is /usr/local/bin/rsync -acv --stats /data/ server::data Any

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #17 from kde@ost.com.sg 2008-05-13 05:25 CST ------- I experienced the same error when rsync to an external usb ide drive. When it happened, the system hanged. Following Andrew Morris with --bwlimit=8192 --timeout=600 setting got rid of system hanging. However, it causes rsync to abort after 600 seconds. The problem is due to

Hello! A good day to you all. i've installed rsync-2.5.6 on a Red Hat 9.0 box(server) and am using rsync 2.5.6 on a Red Hat 6.2 box(client). In the middle of the rsync transfer, i get the error on the client saying that the server unexpectedly close the connection. Upon checking the logs on the rsync server, i found this entry: Oct 10 14:39:38 linux01 rsyncd[9266]: rsync:

Hi everybody, I use RSYNC under windows (cygwin) on both server and client side for syncing 2 big directories over an VPN IPSEC links.(1 GB of data for around 30 000 files). The sync shows these kind of errors for some clients. Here is the command that I use in a batch file to syncing the folders start /w /D "e:/admin/rsyncd/" rsync.exe -az --delete --exclude="SAVE"

https://bugzilla.samba.org/show_bug.cgi?id=1959 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=1959 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-02-27 13:54 ------- To diagnose this bug further, I need a system-call

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From admin@exovian.com 2005-04-21 08:46 ------- root@xxxx [~]# rsync -avz -e ssh /home/ xxxx@xxxxx:xxxx building file list ... rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_entry": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) This method

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:

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #15 from george@imagine-com.com 2007-02-25 04:41 MST ------- Created an attachment (id=2309) --> (https://bugzilla.samba.org/attachment.cgi?id=2309&action=view) log error file rsync command and error massage. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail

Hello, we are using rsync to backup data to a NAS share. The share is mounted with the following command: mount -t nfs 192.168.1.101:/nas/NASDisk-00003/public /media/nas -o timeo=5,rsize=8096,wsize=8096,soft rsync is called by rsnapshot with the command: rsync -a --stats --delete --numeric-ids --relative --delete-excluded /samba /media/nas The process crashes when it tries to copy *.mdb

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

I am trying to execute rsync manually at a "remote" server to test out --read-batch execution. I created the batch files on another server and then rcp'ed them to the "remote" server. I had some issues of not having the correct working directory on the remote system when I did an rsh "remote" rsync --read-batch ...... so I opened a telnet session on the remote

Hello, i386 Platform; FreeBSD v. 7.2 O/S I am experiencing repeated rsync failures, rsyncing from a remote site to which I have no access. >From the client side I can run truss to collect system calls truss -faedD -o truss.out -s 64 /usr/local/bin/rsync -avvv --contimeout=1200 --port=33444 ftp.wwwxxx.org::ftp . >> rsynclog & >From truss.out => 44755: 4492.350089813

I'm attempting to maintain a mirror of a remote database, ~ 66Gb on a FreeBSD platform. I do not have direct access to the database except by rsync, anon. ftp etc. I'm running rsync nightly from crontab, with the cmd /usr/local/bin/rsync -avvv --port=33444 ftp.filesource.org::ftp . >> rsynclog generated the following in the cron report First error [1] rsync error: received SIGINT,

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