HP-UX 11i and largefiles on rsync 2.6.2

Steve Bonds knnf6cy7w001 at sneakemail.com
Wed Jul 14 21:32:07 GMT 2004

On Wed, 14 Jul 2004, Don Malloy nixuser23-at-hotmail.com |Rsync List| wrote:

> The rsync output is as follows:
> server1 # /tmp/rsync --rsync-path=/tmp/rsync --stats file1.db
> server2:/archive1
> 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)

The "Broken pipe" message is what the OS is telling you.  Normally
overflowing a 32 bit offset on write() returns a different error.  "Broken
pipe" means that a connection to a child process (usually) via a pipe has
been suddently severed (usually because the child died before the
filehandle was closed.)

I suspect what has happened is that rsync built with 64 bit file offsets,
but may have used 32-bit offsets for its pipe to the child process.  Or
the child process is crashing for some reason giving you the "Broken pipe"

Try boosting the number of "v" arguments you are using and see if any
useful information pops up as a result.

If you're in a terrible hurry, start an FTP/scp over while debugging the
problem.  You can always use rsync to finish it off if you get the problem
solved (or just wait for FTP if you don't.)

  -- Steve

More information about the rsync mailing list