[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Another failure (was: svn.collab.net intermittent failures)

From: James Goodall <jgoodall_at_dmetrix.com>
Date: 2003-04-14 20:33:51 CEST

FWIW, I just dealt with a similar problem on my repository last Wednesday.
Unfortunately I don't have the bad repository anymore, but I'll tell you
what I can if it might help track this down. The problem started when the
repository wedged after a long checkout (I'm not sure why this happens, but
I have to svnadmin recover the database to clear the locks (?)). When I
tried to recover, I got a similar message to Blair's:

 

>>>$ svnadmin recover repos

>>>Acquiring exclusive lock on repository db.

>>>Recovery is running, please stand by...

>>>Recovery completed.

>>>subversion/libsvn_fs/bdb/bdb-err.c:61: (apr_err=160029)

>>>svn: Berkeley DB error

>>>svn: Berkeley DB error while opening `uuids' table for filesystem
repos/db:

>>>Invalid argument

 

Except that the error was on the 'copies' table instead of the 'uuids'
table. Everything else looks the same. My config is:

OS: Redhat 7.2 w/ all patches

SVN: 0.20.1

Apache: 2.0.44

DB: 4.1.25

 

The odd thing is that the DB log files seem to have been corrupted. I
couldn't restore a working database with just the log files - I kept getting
the same error. The only way I could recover my repository was to rebuild
it from archived dump files.

 

I've been running DB 4.1.25 for months with a couple thousand checkins
without a problem. Since the most recent thing I've upgraded on my system
is SVN, I think we can either assume the problem is either in the latest SVN
or somehow this old problem is coincidently springing up in multiple places
at once.

 

 - James
Received on Mon Apr 14 21:21:49 2003

This is an archived mail posted to the Subversion Dev mailing list.