I started the massive transfer based on the historical timings, but now I am facing lots of problems in the transfer...I am getting lot of errors like this.. This is a very critical production update I have only 3 weeks time to complete this 4 tb transfer that was taken from historical times using rsync rsync: writefd_unbuffered failed to write 4813 bytes: phase "unknown" [sender]: Broken pipe (32) rsync: write failed on "/db31/oradata/sids/w1.dbf": File too large (27) rsync error: error in file IO (code 11) at receiver.c(291) I am running 6 batch files that contain a total of 15500 files and total size of all oracle datafiles is 4 tb. Other info i recently upgraded to RSYNC version "2.6.6 protocol version 29" on destination server... Source server rsync version 2.6.5 protocol version 29 Thanks for your quick help... -- View this message in context: http://www.nabble.com/RSYNC-authors-help-plz...-t1356144.html#a3630993 Sent from the Samba - rsync forum at Nabble.com.
This is the exact error msg from the log....any patches or fix for this.. rsync: connection unexpectedly closed (30 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(434) rsync: writefd_unbuffered failed to write 2897 bytes: phase "unknown" [sender]: Broken pipe (32) rsync: write failed on "/db31/oradata/sids/w1.dbf": File too large (27) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (55 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(434) rsync: connection unexpectedly closed (30 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(434) -- View this message in context: http://www.nabble.com/RSYNC-authors-help-plz...-t1356144.html#a3632194 Sent from the Samba - rsync forum at Nabble.com.
On Tue, Mar 28, 2006 at 06:54:22AM -0800, lsk wrote:> rsync: write failed on "/db31/oradata/sids/w1.dbf": File too large (27)This error is coming from your OS. Either the libraries you linked rsync with do not handle large files, or the destination filesystem does not support files that large. I'd recommend first testing the filesystem for large-file support (if you don't already know this). If that is not the problem, you'll need to figure out why the 2.6.6 build didn't get compiled with large-file support for the functions that it uses: mkstemp() (or mktemp() if your OS didn't have a good enough mkstemp() function), open(), and lseek() all need to be O.K. ..wayne..