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 --progress --log-file=/Volumes/backup/20080429/rsynclog.txt --exclude="*:*" /Volumes/RAID_One /Volumes/backup/20080429 There's a few terabytes of data, and it never finishes a complete run. It can stop at anywhere during the transfer, from 5mins, but usually a few hours into it. on the current issues and debugging section on the website, it mentions how to debug a remote rsync, or daemon, but as far as i know, these dont apply because i'm copying the data on the same machine. See the error log below. Is there anywhere else i can check for errors? Also, what's the characters mean in the logfile, such as:>f..tpog.... RAID_One/data/file8.39M 100% 4.12MB/s 0:00:01 (xfer#3478, to-check=1224/8633) Any help much appreciated. Andrew Logfile: 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) 2008/04/28 20:48:46 [3149] rsync: connection unexpectedly closed (735103 bytes received so far) [sender] 2008/04/28 20:48:46 [3149] rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.0] -------------- next part -------------- HTML attachment scrubbed and removed
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 --progress > --log-file=/Volumes/backup/20080429/rsynclog.txt > --exclude="*:*" /Volumes/RAID_One /Volumes/backup/20080429 > > There's a few terabytes of data, and it never finishes a complete run. > > It can stop at anywhere during the transfer, from 5mins, but usually a > few hours into it. > > on the current issues and debugging section on the website, it > mentions how to debug a remote rsync, or daemon, but as far as i know, > these dont apply because i'm copying the data on the same machine. > > See the error log below. Is there anywhere else i can check for > errors? > > Also, what's the characters mean in the logfile, such as: > >f..tpog.... RAID_One/data/file > 8.39M 100% 4.12MB/s 0:00:01 (xfer#3478, > to-check=1224/8633) > > Any help much appreciated. > Andrew > > > Logfile: > 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4 > bytes [sender]: Broken pipe (32) > 2008/04/28 20:48:46 [3149] rsync: connection unexpectedly closed > (735103 bytes received so far) [sender] > 2008/04/28 20:48:46 [3149] rsync error: error in rsync protocol data > stream (code 12) at io.c(600) [sender=3.0.0] > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html-- Ming Zhang @#$%^ purging memory... (*!% http://blackmagic02881.wordpress.com/ http://www.linkedin.com/in/blackmagic02881 --------------------------------------------
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)That just tells you that the receiver went away. Run a version of rsync that does not have the debug symbols stripped out (i.e. use the binary in the build dir, not the one that is installed), enable core dumps (use "ulimit -c unlimited"), and use a debugger on the core dump to get a backtrace ("gdb /build/dir/rsync core" followed by "bt"). Then, please let me know where it crashed.> Also, what's the characters mean in the logfile, such as: > >f..tpog.... RAID_One/data/file > 8.39M 100% 4.12MB/s 0:00:01 (xfer#3478, to-check=1224/8633)See the --itemize-changes option and the --progress option. ..wayne..