You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Michael Osipov <mi...@apache.org> on 2026/01/10 10:38:05 UTC
Re: svn freezing at checkout on FreeBSD
On 2025/12/21 20:14:38 Anton Shepelev wrote:
> Hello, all.
>
> On FreeBSD 14.3, svn 1.14.2 freezes at the checkout operation of an
> svn:// repository. The working-directory is created together with the
> .svn subdirectory, but nothing else appears. If I kill the fronzen
> svn process, and do `svn up', it says the working copy is already locked.
> If I do `svn cleanup', then `svn up' hangs forever as well.
>
> I have made sure that both /dev/random and /dev/urandom do not
> block, by reading a single byte from them:
>
> od -vAn -N2 -tu2 < /dev/random
> od -vAn -N2 -tu2 < /dev/urandom
>
> On FreeBSD, /dev/urandom is a symlink to /dev/random, but it
> did not stop other and previous installation of FreeBSD.
> Please, help me shoot this trouble, preferable in the head
> rather than in the foot.
I can confirm that on my end. I had those freezes in various Subversion versions and FreeBSD versions over the past could of years where the client and the server are on the same machine accessed via HTTPS. I always assumed that is was my setup and never analyzed it. It is hard to reproduce. Most of the time it has happended when:
* Updated 100+ working copies at once in a loop
* Performed "mvn release:prepare release:perform"
I'd behappy to trace when this happens again, but need to know what exactly. truss? Wireshark?
Michael
Re: svn freezing at checkout on FreeBSD
Posted by Daniel Sahlberg <da...@gmail.com>.
Den lör 10 jan. 2026 kl 11:38 skrev Michael Osipov <mi...@apache.org>:
> On 2025/12/21 20:14:38 Anton Shepelev wrote:
> > Hello, all.
> >
> > On FreeBSD 14.3, svn 1.14.2 freezes at the checkout operation of an
> > svn:// repository. The working-directory is created together with the
> > .svn subdirectory, but nothing else appears. If I kill the fronzen
> > svn process, and do `svn up', it says the working copy is already locked.
> > If I do `svn cleanup', then `svn up' hangs forever as well.
> >
> > I have made sure that both /dev/random and /dev/urandom do not
> > block, by reading a single byte from them:
> >
> > od -vAn -N2 -tu2 < /dev/random
> > od -vAn -N2 -tu2 < /dev/urandom
> >
> > On FreeBSD, /dev/urandom is a symlink to /dev/random, but it
> > did not stop other and previous installation of FreeBSD.
> > Please, help me shoot this trouble, preferable in the head
> > rather than in the foot.
>
> I can confirm that on my end. I had those freezes in various Subversion
> versions and FreeBSD versions over the past could of years where the client
> and the server are on the same machine accessed via HTTPS. I always assumed
> that is was my setup and never analyzed it. It is hard to reproduce. Most
> of the time it has happended when:
> * Updated 100+ working copies at once in a loop
> * Performed "mvn release:prepare release:perform"
>
> I'd behappy to trace when this happens again, but need to know what
> exactly. truss? Wireshark?
>
> Michael
>
A Wireshark trace is always nice - then it might be possible to see who is
waiting for what. Of course, if it is hard to reproduce... To me it sounds
a lot like package loss (which should be handled on the TCP level or
suitably reported as a socket error).
Cheers,
/Daniel
Re: svn freezing at checkout on FreeBSD
Posted by Anton Shepelev <an...@gmail.com>.
Michael Osipov:
> I can confirm that on my end. I had those freezes in
> various Subversion versions and FreeBSD versions over
> the past could of years where the client and the
> server are on the same machine accessed via HTTPS.
A situation very much different from mine: svn:// and
different client and server machines connected over
mobile internet.
> I always assumed that is was my setup and never
> analyzed it. It is hard to reproduce.
I can stably reproduce it by checking out a tiny repo
directrly from the Subversion server instead of over an
SSH tunnel.
> Most of the time it has happended when:
> * Updated 100+ working copies at once in a loop
> * Performed "mvn release:prepare release:perform"
The lattter command is Maven interacting with
Subversion?
> I'd behappy to trace when this happens again, but need
> to know what exactly. truss? Wireshark?
I can even provoide SSH access to the machine where this
happens.