> From: sussman@collab.net [mailto:sussman@collab.net]
> Sent: Friday, August 29, 2003 4:09 PM
> "Sander Striker" <striker@apache.org> writes:
>
> > I'll give the subversion dataset a go to see if that makes a difference.
>
> Sander and I have been testing this morning, and I'm able to reproduce
> the repsitory 'hang' very, very easily. Here's my recipe:
I've been able to reproduce with the following similar scenario:
> * I'm running httpd-2.0.47 on http://localhost, and I'm exporting a
> personal copy of svn's own repository at /svn/bigrepos.
The dataset seems to be important. Like I said, earlier tests with
my repos of the mozilla tree didn't fail.
> * I start three svn clients, have them each checkout
> http://localhost/svn/bigrepos/trunk simultaneously.
However, I get the following:
$ svn co http://localhost/svn/svn/trunk svn-trunk-wc1
A svn-trunk-wc1/Makefile.in
A svn-trunk-wc1/ac-helpers
A svn-trunk-wc1/ac-helpers/install.sh
A svn-trunk-wc1/ac-helpers/install-sh
A svn-trunk-wc1/build.conf
A svn-trunk-wc1/win-tests.py
A svn-trunk-wc1/www
subversion/libsvn_ra_dav/util.c:331: (apr_err=160029)
svn: Berkeley DB error
svn:
Berkeley DB error while beginning Berkeley DB transaction for filesystem /home/striker/repositories/subversion/db:
DB_RUNRECOVERY: Fatal error, run database recovery
The other two clients fail before being able to get their first file.
This is nasty...
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 29 17:23:37 2003