similar to: [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe

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

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 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 ------- 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

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 ---------------------------------------------------------------------------- Severity|major |normal Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-10-21 15:19

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

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

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

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

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:

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,

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

https://bugzilla.samba.org/show_bug.cgi?id=3488 Summary: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32) Product: rsync Version: 2.6.6 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P3 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=5478 Summary: rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32) Product: rsync Version: 3.0.3 Platform: Other URL: https://bugzilla.samba.org/show_bug.cgi?id=1959 OS/Version: Linux Status: NEW Severity: normal

https://bugzilla.samba.org/show_bug.cgi?id=2208 Summary: rsync failed at random file with same error rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at

Hi All. On Mac OS10.4, using rsync 3.0, it stops during a transfer. I mount an SMB share, and then use the line: sudo rsync -avhi --delete --stats --timeout=360 --progress --log-file=/Volumes/backup/20080429/rsynclog.txt --exclude="*:*" /Volumes/RAID_One /Volumes/backup/20080429 There's a few terabytes of data, and it never finishes a complete run. It can stop at anywhere during

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

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'm experiencing some unexpected behavior with rsync v2.5.6. After looking around it seems like several people have experienced similar problems in the past, but those appear to be old bugs that are solved now. Also doesn't appear to be any direct bugfixes made for this issue since 2.5.6. The strange thing is that things seem to work when I use ssh for transport. However now I need to