On Tuesday 03 February 2004 02:06, Karl Chen wrote:
> I got this scary error message:
>
> (I did a commit which worked normally, then an update in another
> directory failed with: )
>
> svn: Berkeley DB error while opening 'uuids' table for filesystem quarl/db:
> Invalid argument
>
>
> $ svnadmin recover quarl
> Acquiring exclusive lock on repository db.
> Recovery is running, please stand by...
> Recovery completed.
> svn: Berkeley DB error
> svn: Berkeley DB error while opening 'uuids' table for filesystem quarl/db:
> Invalid argument
>
>
> I noticed that the db/uuid file hadn't changed in any of the
> previous backups, so I made a copy of the repos plus the old
> 'uuid', and things seem to work.
>
> Server: Debian unstable packages, i.e. subversion 0.33.0, libapr0
> 2.0.48, libdb4.1 4.1.25
>
> Client: subversion 0.37.0
We've been seeing a lot more of this lately with Debian users. The problem (I
believe) stems from the fact that your version on the server is built against
BDB 4.1.25. As Justin has pointed out in one email, 4.1.25 has problems in
its shared memory implementation.
I recommend going to sleepycat.com and getting the latest version (4.2.52) and
recompiling apache2 and subversion. You should upgrade to the latest
subversion too, since you get features such as automatic log file cleanup
when used in conjuction with BDB 4.2.x.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 3 11:00:36 2004