Hi I am having trouble with intermittent timeouts when backing up a largish set of files from /usr using rsync. Approx 125,000 files, 2GB. Backup is to same machine, from a partition on hda to one on hdb. I am using ribs 2.1 (slightly modified to ignore rsync error 23), run with nice -n 5 via cron. (for ribs visit http://rustyparts.com/phpBB/viewforum.php?f=9 ) Typical error report is: rsync error: timeout in data send/receive (code 30) at io.c(103) rsync: connection unexpectedly closed (2613404 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) rsync: connection unexpectedly closed (2613404 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) rsync return value = 12 The rsync command being generated by ribs is: /usr/bin/rsync -artpl --delete --delete-excluded --stats --timeout=600 --exclude="/usr/local/*" -e ssh "root@localhost:/usr" /backups/hdb/system/usr/weekly.0 >/tmp/ribs-system-weekly_b4tInu 2>&1 I've just run this from the command line (at default priority) and it took only 7 minutes to complete. Increasing the timeout from 180 (ribs default) to 600 has not improved matters. On the other hand a 6GB set of files, mostly jpegs, appears to be handled reliably. As are all my other ribs backups via cron, generally a few 100MB. Mandrake 9.2, rsync 2.5.6, open ssh 3.6.1p2. Any suggestions? Thanks ...John -- ------------------------------------------------------------ John Hunt Stokesley, N Yorks, UK e-mail: jrhunt@iee.org URL: http://www.yoredale.uklinux.net/ ------------------------------------------------------------
On Tue, Jan 13, 2004 at 06:50:28PM +0000, John Hunt wrote:> Hi > > I am having trouble with intermittent timeouts when backing up a largish set > of files from /usr using rsync. Approx 125,000 files, 2GB. Backup is to same > machine, from a partition on hda to one on hdb. I am using ribs 2.1 > (slightly modified to ignore rsync error 23), run with nice -n 5 via cron. > (for ribs visit http://rustyparts.com/phpBB/viewforum.php?f=9 ) > > Typical error report is: > > rsync error: timeout in data send/receive (code 30) at io.c(103) > rsync: connection unexpectedly closed (2613404 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(165) > rsync: connection unexpectedly closed (2613404 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(165) > > rsync return value = 12 > > The rsync command being generated by ribs is: > > /usr/bin/rsync -artpl --delete --delete-excluded --stats --timeout=600 > --exclude="/usr/local/*" -e ssh "root@localhost:/usr" > /backups/hdb/system/usr/weekly.0 >/tmp/ribs-system-weekly_b4tInu 2>&1 > > I've just run this from the command line (at default priority) and it took > only 7 minutes to complete. Increasing the timeout from 180 (ribs default) to^^^^^^^^ I assume you mean fail.> 600 has not improved matters. > > On the other hand a 6GB set of files, mostly jpegs, appears to be handled > reliably. As are all my other ribs backups via cron, generally a few 100MB. > > Mandrake 9.2, rsync 2.5.6, open ssh 3.6.1p2. > > Any suggestions?It sounds like a something is causing a hang. I'd start by adding -v to see when it is hanging. Perhaps -vv. You might want to fsck the filesystem. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt
On Tuesday 13 Jan 2004 22:15, jw schultz wrote:> You > might want to fsck the filesystem.Both partitions check out ok (e2fsck -fcv) -- ------------------------------------------------------------ John Hunt Stokesley, N Yorks, UK URL: http://www.yoredale.uklinux.net/ ------------------------------------------------------------
On Tuesday 13 Jan 2004 18:50, John Hunt wrote:> Hi > > I am having trouble with intermittent timeouts when backing up a largish > set of files from /usr using rsync. Approx 125,000 files, 2GB. Backup is to > same machine, from a partition on hda to one on hdb. I am using ribs 2.1 > (slightly modified to ignore rsync error 23), run with nice -n 5 via cron. > (for ribs visit http://rustyparts.com/phpBB/viewforum.php?f=9 ) > > (snip)I am fairly confident I have found the cause. It was my fault, not rsync's :-( I run gimps (Mersenne prime search) in the background at lowest priority. Except that during a system upgrade last month I made an error with the gimps startup (in rc.local) with result that it was running at priority higher than my cron jobs. Compounded by me allowing gimps to use a large fraction of physical memory overnight if it wants to - though whether it actually does is unclear. I had forgotten that the cron rsync jobs also run overnight. rsync was almost certainly reporting a genuine timeout caused by it being starved of CPU time and possibly memory. I run the large rsync backup only once a week, so too soon to be sure the problem is resolved. However this week's backup ran ok via cron for the first time so looks promising. -- ------------------------------------------------------------ John Hunt Stokesley, N Yorks, UK URL: http://www.yoredale.uklinux.net/ ------------------------------------------------------------