rsync - Jun 2004 - [Bug 1457] 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:
http://www-1.ibm.com/servers/aix/products/aixos/linux/download.html

This also happens for current rsync version 2.6.2 built using gcc 2.9
(The gcc is built by IBM available from same URL as above). The error with
rsync 2.6.2 is shown below.

$ ls -l
-rw-r--r--   1 oracle   oinstall 4666171392 Jun 11 23:30 maxdataMXPDB02.dbf

$ rsync -av maxdataMXPDB02.dbf /net02/oracle/

building file list ... done
maxdataMXPDB02.dbf

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)


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=1457





------- Additional Comments From mwang@unixlabplus.com  2004-06-13 12:32 -------
The problem occurs when both the source and destionation are locally mounted 
file systems. In the words, the problem is not related with network at all.

As a matter of fact, I actually successfully transferred a > 6GB file over
the
network to a Solaris 8 box from AIX 5.2.

So this seems to indicate network is ok, local has the problem.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=1457





------- Additional Comments From wayned@samba.org  2004-06-14 07:30 -------
Did you investigate why the temp file could not be created?

/mnt/zip/zip750/zip750/C/.2b.c.v2TNLo

I would imagine that the zip disk is either full or that its file system
doesn't
support large files.  Remember that you must have enough free space to store an
extra copy of the largest transferred file that is being updated (or you must
use the --temp-dir option to force the temp file onto another disk).

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=1457





------- Additional Comments From markf78@yahoo.com  2004-06-14 09:24 -------
using the switch --temp-dir solves my problem.. sorry for the incovenience.
thanks.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=1457


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From wayned@samba.org  2004-06-14 10:04 -------
Looks like a zip-disk overflow -- closing.

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.