rsync - Sep 2001 - problems with large transfers form solaris 2.6

Hi all.

I have a large data set on solaris 2.6 (approx 16gb and about 900K files and
rectory structures). Rsync is misbehaving in the most obnoxious way:

it is launched as such: rsync -e ssh -aLv --bwlimit=512 --timeout=300
<source> <dest>

A transfer starts, a list of files and directories is built, and data starts
flowing. then for no apparent reason data stops flowing form the rsync on the
solaris end the the connection times out after 5 minutes of no IO activity. When
the timeout parameter is not there, the rsync will just stop and hang around for
hours untill killed.

The only other this worth mentioning is that the solaris box is hidden behind a
firewall and we use a ssh proxy (TIS plug proxy) to connect to the box.

Addibd many v's on the commandline produces a lot of debug but no real
information as to whats going on. The data flow just stops and there is no error
messages on either end in rsync output or logs... I am stumped... I wander is
there is no known issues with globbing functions (if rsync uses them) on solaris
or some such...

Any isnights or pointers would be appreceated.

Regards
Tomasz Ciolek


-- 
Tomasz M. Ciolek	*
			* 	Everything falls under the law of change;	
<tmc@dreamcraft.com.au>	*	  Like a dream, a phantom, a bubble, a shadow,
<tmc@goldweb.com.au>	*	  like dew of flash of lightning.
			*	  You should contemplate like this. 
*******************************************************************************
GPG Key ID: 0x7A18E49D	*	Available on www.pgp.net
*******************************************************************************

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url :
http://lists.samba.org/archive/rsync/attachments/20010926/16d73017/attachment.bin

On Wed, Sep 26, 2001 at 10:46:51AM +1000, Tomasz Ciolek
wrote:
> Hi all.
> 
> I have a large data set on solaris 2.6 (approx 16gb and about 900K files
> and rectory structures). Rsync is misbehaving in the most obnoxious way:
> 
> it is launched as such: rsync -e ssh -aLv --bwlimit=512 --timeout=300
<source> <dest>
> 
> A transfer starts, a list of files and directories is built, and data
> starts flowing. then for no apparent reason data stops flowing form the
> rsync on the solaris end the the connection times out after 5 minutes of no
> IO activity. When the timeout parameter is not there, the rsync will just
> stop and hang around for hours untill killed.
> 
> The only other this worth mentioning is that the solaris box is hidden
> behind a firewall and we use a ssh proxy (TIS plug proxy) to connect to the
> box.
> 
> Addibd many v's on the commandline produces a lot of debug but no real
> information as to whats going on. The data flow just stops and there is no
> error messages on either end in rsync output or logs... I am stumped... I
> wander is there is no known issues with globbing functions (if rsync uses
> them) on solaris or some such...
> 
> Any isnights or pointers would be appreceated.
What version of rsync is running on both sides, and what version of ssh are
you using?  There have been versions of both that have hanging problems,
and there are even patches available for the current version of rsync
although I'm not sure whether they're relevant over ssh.  People have
reported that the "-v" option makes things worse.  Using
"netstat" on both
sides (and probably on your proxy machine too) may help to detect where
packets are piling up in queues.

- Dave Dykstra