In message <[EMAIL PROTECTED]> you write:
> If I understood Andrew's mail correctly, rsync freezes when
> large amount of errors happen. Particularly, here ssh always freezes
Known hard-to-fix bug in rsync; too many errors in the pipe, and it
locks up.
Rusty.
--
Premature optmztion is rt of all
Hello!
> Well, since I moved the rsync to 5pm, and then back to 9pm, I haven't
> seen this problem - everything is again working as expected (touch wood)
> with 2.2.15pre13 and 2.4.0.
>
> This is odd, since it wasn't a one-off problem, but something that happened
> each and every day of a partic
On Wed, Feb 28, 2001 at 11:20:22PM +0300, [EMAIL PROTECTED] wrote:
> I remember this your report. However, recent news force to suspect
> that the reason was in Solaris yet. Actually, if you send tcpdump of
> failed session, this question can be answered.
Well, since I moved the rsync to 5pm, and
Hello!
> I'll see if I can strace it from the start until it hangs tomorrow.
Please...
Also, try to make binary tcpdump.
> I was running at one point a 2.4.0-test kernel, but I didn't see these
Yes, it did not result in full stall. Lost wakeups were recovered
f.e. by any keyboard activity. 8
Hello!
> I've seen hanging rsync over ssh more than once, while sending much data
> from an x86 running Linux (late 2.3.x) to Sparc/Solaris2.5.1
I remember this your report. However, recent news force to suspect
that the reason was in Solaris yet. Actually, if you send tcpdump of
failed session,
In article <[EMAIL PROTECTED]>,
Russell King <[EMAIL PROTECTED]> writes:
> I'm seeing odd behaviour with rsync over ssh between two x86 machines -
I've seen hanging rsync over ssh more than once, while sending much data
from an x86 running Linux (late 2.3.x) to Sparc/Solaris2.5.1 over ss
[EMAIL PROTECTED] writes:
> Moreover, even not _one_ wakeup is missing. At least two, because
> wakeups in read and write are separate and you have stuck in both directions.
> 8)8)
I'll see if I can strace it from the start until it hangs tomorrow.
> Well, if it was one I would start to dig grou
David S. Miller writes:
> How do you know this? There are so many deadly TCP bugs fixed
> since 2.2.15pre13 I don't know how you can assert this.
Through the evidence I gave.
Firstly, if the receiving side is saying that it has a window of 0, then
it is not going to accept any more data.
Sec
Hello!
> netstat on isdn-gw shows the following:
>
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp72868 0 isdn-gw.piltdown.a:1023 pilt-gw.piltdown.at:ssh ESTABLISHED
plus
> select(4, [3], [3], NULL, NULL) = 2 (in [3], out [3])
> Ma
Anton Blanchard writes:
> > I'm seeing odd behaviour with rsync over ssh between two x86 machines -
> > one if the is an UP PIII (Katmai) running 2.4.2 (isdn-gw) and the other
> > is an UP Pentium 75-200 (pilt-gw) running 2.2.15pre13 with some custom
> > serial driver hacks (for running Amplicon c
Hi,
> I'm seeing odd behaviour with rsync over ssh between two x86 machines -
> one if the is an UP PIII (Katmai) running 2.4.2 (isdn-gw) and the other
> is an UP Pentium 75-200 (pilt-gw) running 2.2.15pre13 with some custom
> serial driver hacks (for running Amplicon cards with their ISA interr
On Tue, Feb 27, 2001 at 11:18:39AM +0100, Rasmus Andersen wrote:
> terminate, apparently because the child does not receive the KILLUSR1
> (wild speculation)? Anyways, the parent process waits in wait4 and
> the child loops, waiting for the signal. This is not reproducable
> in 2.2.X (for me).
r
Russell King writes:
> Please note: although I am using 2.2.15pre13, it is _not_ the cause of
> this problem
How do you know this? There are so many deadly TCP bugs fixed
since 2.2.15pre13 I don't know how you can assert this.
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from th
On Tue, Feb 27, 2001 at 10:02:11AM +, Russell King wrote:
> Hi,
>
> I'm seeing odd behaviour with rsync over ssh between two x86 machines -
> one if the is an UP PIII (Katmai) running 2.4.2 (isdn-gw) and the other
> is an UP Pentium 75-200 (pilt-gw) running 2.2.15pre13 with some custom
> seri
Hi,
I'm seeing odd behaviour with rsync over ssh between two x86 machines -
one if the is an UP PIII (Katmai) running 2.4.2 (isdn-gw) and the other
is an UP Pentium 75-200 (pilt-gw) running 2.2.15pre13 with some custom
serial driver hacks (for running Amplicon cards with their ISA interrupt-
shar
15 matches
Mail list logo
