Reliability and robustness problems

John rsync at computerdatasafe.com.au
Fri Jun 11 00:14:39 GMT 2004


Wayne Davison wrote:

>On Wed, Jun 09, 2004 at 09:42:08PM +0800, John wrote:
>  
>
>>I will install 2.6.2 when the backup run has completed, but I want the 
>>current run to complete first.
>>    
>>
>
>Since you're using multiple sources with --delete, make sure the 2.6.2
>code you compiled has been patched with the simple fix attached to this
>bug report:
>
>https://bugzilla.samba.org/show_bug.cgi?id=1413
>
>..wayn
>  
>

I don't yet have that patch in place, so my next run won't be on the new 
version.

This one has completed, with a timeout:
+ rsync --recursive --links --hard-links --perms --owner --group 
--devices --times --sparse --one-file-system --rsh=/usr/bin/ssh --delete 
--delete-excluded --delete-after --max-delete=80 --relative --stats 
--numeric-ids --timeout=3600 /var/local/backups 
192.168.0.1:/var/local/backups/
io timeout after 3600 seconds - exiting
rsync error: timeout in data send/receive (code 30) at io.c(85)

real    3001m51.871s
user    14m32.230s
sys     4m26.440s

As you can see, I don't have any stats on its performance.

I'm about to restart it, based on this I expect the next run to finish 
catching up.


Regarding the patch, I intend to put together a procedure that works, or 
reliably fails. I'll report back on this thread when I have an outcome.




More information about the rsync mailing list