Thanks for the suggestion Steve.
Here is the output with -vvv in the local rsync:
------------------
server2 # /usr/local/bin/rsync -avvv --progress --stats file1.db /var/opt/ignite/test
building file list ...
[sender] make_file(file1.db,*,2)
[sender] expand file_list to 131072 bytes, did move
1 file to consider
send_file_list done
send_files starting
server_recv(2) starting pid=24974
recv_file_name(file1.db)
received 1 names
recv_file_list done
get_local_name count=1 /var/opt/ignite/test
recv_files(1) starting
generator starting pid=24974 count=1
delta-transmission disabled for local transfer or --whole-file
recv_generator(file1.db,0)
send_files(0, file1.db)
send_files mapped file1.db of size 4304863232
calling match_sums file1.db
file1.db
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)
_exit_cleanup(code=12, file=io.c, line=836): about to call exit(12)
------------------
Just reading another post on the list, an rsync --version shows:
rsync version 2.6.2 protocol version 28 Copyright (C) 1996-2004 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 32-bit system inums, 64-bit internal inums
rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details.
Is it supposed to show 32-bit system inums? Will this require a re-compile and how do I force that parameter to 64-bit?
Thanks again, Don
From: "Steve Bonds" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2 Date: Wed, 14 Jul 2004 14:32:07 -0700 (PDT)
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" message.
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
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
-- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
