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

Re: Corrupted repository report

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-06-17 18:31:19 CEST

On Thu, 2004-06-17 at 11:20, Scott Lawrence wrote:

> Transmitting file data .........................svn: Commit failed (details follow):
> svn:
> Berkeley DB error while committing Berkeley DB transaction for filesystem /scm/rep/sipXtackLib/db:
> Invalid argument

This looks like a BDB 4.1 bug we've seen before, whereby a table's type
gets mysteriously changed. Is that what you're using? If so, we
recommend rebuilding apache's apr-util to use BDB 4.2 ASAP.

> so I ran 'svnadmin recover' on it and got:
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery

Did you try catastrophic recovery? 'db_recover -cve -h repos/db/'

> The bad repository can be downloaded from:
> http://www.sipfoundry.org/tmp/sipXtackLib_broken.tar.bz

Maybe MaxB or cmpilato can take a look at it.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 17 18:33:32 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.