io timeout

[Eric Whiting]

I've had this same problem with 2.4.7pre1. I thought it was due to
problems with the link, but perhaps we have a rsync issue here. These
connections  timeout on 100M files -- but the link is quite slow. 

Here are the errors from my last night rsync to a large group of hosts.



ic_craft/penking1.errors:io timeout after 6000 seconds - exiting
ic_craft/penking1.errors:rsync error: timeout in data send/receive (code
30) at io.c(68)
silvaco/penharte.errors:io timeout after 6000 seconds - exiting
silvaco/penharte.errors:rsync error: timeout in data send/receive (code
30) at io.c(68)
silvaco/penking1.errors:io timeout after 6001 seconds - exiting
silvaco/penking1.errors:rsync error: timeout in data send/receive (code
30) at io.c(68)
silvaco/penktgp.errors:io timeout after 6000 seconds - exiting
silvaco/penktgp.errors:rsync error: timeout in data send/receive (code
30) at io.c(68)
synopsys/penking1.errors:io timeout after 6000 seconds - exiting
synopsys/penking1.errors:rsync error: timeout in data send/receive (code
30) at io.c(68)




Carey Jung wrote:
> 
> Hi,
> 
> We're running the rsync 2.4.7 pre-release to backup a number of servers to a
> central backup server, all running Linux 2.2.17 kernel.   We moved up to
> 2.4.7, hoping it would fix the 'unexpected EOF' errors which we were getting
> everytime we'd run more than a handful of rsyncs at the same time.  Initial
> tests have not shown the EOF errors.    However, on one backup, when rsync
> hits a very large (2 GB) file, it eventually times out with "io timeout
> after 3614 second - exiting".  (Our timeout is set to 3600 seconds.)
> 
> Is this to be expected, and do I just need to bump out timeout to account
> for such large files (over a moderate SDSL connection)?
> 
> Regards,
> Carey