Re: Another rsync over ssh hang (repeatable, with 2.4.1 on both ends)
Tim Wright (firstname.lastname@example.org)
Fri, 2 Mar 2001 11:45:41 -0800
On Fri, Mar 02, 2001 at 10:12:36AM +0000, Russell King wrote:
> On Thu, Mar 01, 2001 at 04:41:01PM -0800, Scott Laird wrote:
> > I have a fairly repeatable rsync over ssh stall that I'm seeing between
> > two Linux boxes, both running identical 2.4.1 kernels. The stall is
> > fairly easy to repeat in our environment -- it can happen up to several
> > times per minute, and usually happens at least once per minute. It
> > doesn't really seem to be data-sensitive. The stall will last until the
> > session times out *unless* I take one of two steps to "unstall" it. The
> > easiest way to do this is to run 'strace -p $PID' against the sending ssh
> > process. As soon as the strace is started, rsync starts working again,
> > but will stall again (even with strace still running) after a short period
> > of time.
> > According to 'ps l', the ssh process is waiting in 'sock_wait_for_wmem'.
> I've also reported this recently, and got told that it was because I was
> running 2.2.15pre13 on one end. Thanks for confirming that 2.2.15pre13
> is not the cause.
Be very careful here. He did nothing of the sort. He merely indicated that
there is at least one problem running rsync over ssh between 2.4.1 systems.
There is no guarantee that your problem and his are identical. As Alexey
pointed out, there are bad bugs in 2.2.15 which can cause a TCP connection to
get stuck. Given that you are running 2.2.15, you'd need a tcpdump to
determine whether you hit one of these or not.
I've been bitten too many times assuming something was one big problem only
to find out later it was actually several smaller ones.
Tim Wright - email@example.com or firstname.lastname@example.org or email@example.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/