Re: writefd_unbuffered failed (when writing to micro SD cards)

Just got a brand new micro SD card and it's also throwing the error. Any ideas? How can I troubleshoot this more deeply? Christopher de Vidal (You're a good person? If you can prove it, take the money. This is a legitimate offer. TenThousandDollarOffer.com) On Wed, Apr 17, 2013 at 8:17 AM, Chris

Re: "writefd_unbuffered failed to write 4092 bytes to socket"

Hi, If you are able to rsync over ssh, this connection may be more robust than plain rsync protocol. See http://www.mail-archive.com/rsync@lists.samba.org/msg26280.html Best regards, Vitorio -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change

Re: "writefd_unbuffered failed to write 4092 bytes to socket"

On Sat, 2010-09-25 at 07:33 -0700, Joseph Maxwell wrote: > 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/loca

Re: writefd_unbuffered failed - Broken pipe on local rsync

On Wed, 2010-03-10 at 11:58 +, Dave Howorth wrote: > 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 >

Re: writefd_unbuffered failed to write

On Tue, 2008-10-21 at 22:54 +0200, Matthias Meyer wrote: > In the server logfile I see: > full backup started for directory D (baseline backup #8) > Connected to Loredana.mybackup:10025, remote version 30 > Negotiated protocol version 28 > Connected to module D > Sending > args: --server --sender

Re: writefd_unbuffered failed to write 4 bytes

On Mon, May 05, 2008 at 08:12:43AM +1000, Ramkumar Santoshi wrote: > once i compile rsync, the 'rsync' in the current dir should be ok for this? Right. > can you please explain each step from then? I listed the steps in the prior email, but here they are with a little more detail: Enable core d

Re: writefd_unbuffered failed to write 4 bytes

ok, perhaps we can go back to the start so i know where we are... once i compile rsync, the 'rsync' in the current dir should be ok for this? can you please explain each step from then? much appreciated. On Sat, May 3, 2008 at 1:00 AM, Wayne Davison <[EMAIL PROTECTED]> wrote: > On Fri, May 02

Re: writefd_unbuffered failed to write 4 bytes

On Fri, May 02, 2008 at 12:38:12PM +1000, Ramkumar Santoshi wrote: > I'm pretty sure i grabbed the one from the build dir. Is there any way i > can tell? You can look at the size and/or see if "file rsync" output "stripped" or "not stripped". ..wayne.. -- Please use reply-all for most replies t

Re: writefd_unbuffered failed to write 4 bytes

Thanks Wayne. I'm pretty sure i grabbed the one from the build dir. Is there any way i can tell? On Thu, May 1, 2008 at 12:17 AM, Wayne Davison <[EMAIL PROTECTED]> wrote: > On Tue, Apr 29, 2008 at 10:05:07AM +1000, Ramkumar Santoshi wrote: > > On Mac OS10.4, using rsync 3.0, it stops during a

Re: writefd_unbuffered failed to write 4 bytes

On Tue, Apr 29, 2008 at 10:05:07AM +1000, Ramkumar Santoshi wrote: > On Mac OS10.4, using rsync 3.0, it stops during a transfer. That's an incomplete version. The last release was 3.0.2. > 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4 bytes > [sender]: Broken pipe (32)

Re: writefd_unbuffered failed to write 4 bytes

FYI, I saw this in rsync3 from time to time as well. Ming On Tue, 2008-04-29 at 10:05 +1000, Ramkumar Santoshi wrote: > 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

Re: writefd_unbuffered failed to write 32768 bytes: phase

Dag Wieers wieers.com> writes: > > 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

Re: writefd_unbuffered failed to write - Broken pipe

On Sat, Oct 09, 2004 at 11:39:45AM -0700, Saunders, Shawn wrote: > 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(842) A broken-pipe error means that the other end of the connection went awa

Re: writefd_unbuffered failed

Hello, Yes, both client and server are clean...but i think i know what the problem is now. Server is using an ext3 fs, the client ext2 -- and trying to rsync a >2gb file over to the client B). i'll compile in ext3 support and try again. Thanks! Jim Salter <[EMAIL PROTECTED]> wrote:

Re: writefd_unbuffered failed

> 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: writefd_unbuffered failed to write 4096 bytes: phase "u