-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, all,
this is no longer in the SVN ballpark.
The story continues over at
http://bugzilla.openvz.org/show_bug.cgi?id=1443 .
I apologize for any SVN developer resources wasted by this!
Andreas
- --
Dr. Andreas Krüger, Berater, DV-RATIO NORDWEST
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo, Philip,
management summary: It does look like svnserve is innocent and
openvz's write call is to blame after all!
Firstly, I have now been able to move this entire affair off my
internet "production" server.
The bug is reproducible locally, o
"Dr. Andreas Krüger" writes:
>> strace should show you whether or not the server is writing any
>> data, and whether or not the writes are failing. Is it writing any
>> data at all?
> Yes.
>
>> Are the writes failing?
>
> No!
How big are the writes? In my test I saw things like:
write(4, " )
"Dr. Andreas Krüger" writes:
>> I tried to reproduce your problem without using OpenVZ.
>
> thanks for trying! (Though I don't think you have succeeded.)
I suppose it might be an openvz-only bug.
> I'm not complaining about "slow". I'm complaining about "no progress
> at all" and "endless loop"
On Mon, Mar 01, 2010 at 03:58:00PM +0100, "Dr. Andreas Krüger" wrote:
> So, as I said, this line of investigation lead nowhere.
Can you attach gdb to the spinning svnserve (with debug symbols)
and get a trace of where and how it's spinning?
Stefan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, Philip,
> I tried to reproduce your problem without using OpenVZ.
thanks for trying! (Though I don't think you have succeeded.)
To follow your request, while the stuck download was running and
getting nowhere, I did two "ls -laR" on the clien
"Dr. Andreas Krüger" writes:
> I also see
> several poll timeouts
>
> poll([{fd=0, events=POLLIN}], 1, 0) = 0 (Timeout)
>
> and several successful brk calls, before it finally all starts over again.
>
> More or less over again, that is. There seems to be an _llseek into
> that revision file t
Hi Andreas,
thank you for reporting this problem. I am sorry to see that you have
received no helpful replies yet. That's probably because many of us are tied
up on the road to 1.7.
Let me assure you that your mail has arrived in our inboxes. I hope someone
familiar with svnserve can reproduce an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
> He additionally reports that this is reproducible not only with
> 1.5.1, but with Debian's build of 1.6.9. (That mail is probably in
> the moderation queue now.)
thank you Peter! (To me, this is the first indication that someone
actually no
[Dr. Andreas Krüger]
> I run svnserve under Linux under inetd, with low memory allowances
> for TCP send buffers.
>
> Checkout on the client side causes svnserve to burn CPU cycles,
> apparently endlessly without making any progress.
He additionally reports that this is reproducible not only wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, all,
in short:
* The bug is reproducible with svnserve 1.6.
* The bigger the files get, the more TCP sendbuffer svnserve seems to
need.
Minute detail:
Installing
> Package: subversion Version: 1.6.4dfsg-1~bpo50+1
and
> Package: libsvn1 Ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can also cut out the inetd entirely.
svnserve -d --listen-port=3691 --foreground -r path-to-repository
shows the same partial checkout on the client, then hanging, and CPU
consumption on the server.
Regards,
Andreas
- --
Dr. Andreas Krüger, Berat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I run svnserve under Linux under inetd, with low memory allowances for
TCP send buffers.
Checkout on the client side causes svnserve to burn CPU cycles,
apparently endlessly without making any progress.
Here are the gory details:
My Setup
=
13 matches
Mail list logo
