From: Russell King <rmk@arm.linux.org.uk>
To: Scott Laird <laird@internap.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Another rsync over ssh hang (repeatable, with 2.4.1 on both ends)
Date: Fri, 2 Mar 2001 10:12:36 +0000 [thread overview]
Message-ID: <20010302101236.A21799@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0103011607540.17365-100000@laird.ocp.internap.com>
In-Reply-To: <Pine.LNX.4.33.0103011607540.17365-100000@laird.ocp.internap.com>; from laird@internap.com on Thu, Mar 01, 2001 at 04:41:01PM -0800
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.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-03-02 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 0:41 Another rsync over ssh hang (repeatable, with 2.4.1 on both ends) Scott Laird
2001-03-02 10:12 ` Russell King [this message]
2001-03-02 15:47 ` kuznet
2001-03-02 16:31 ` Russell King
2001-03-02 17:06 ` Ben Collins
2001-03-02 18:08 ` kuznet
2001-03-02 18:35 ` Scott Laird
2001-03-02 19:45 ` Tim Wright
2001-03-04 21:28 ` Ton Hospel
2001-03-03 15:42 ` kuznet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010302101236.A21799@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=laird@internap.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.