[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: Scott Lawrence <slawrence_at_pingtel.com>
Date: 2004-06-17 19:19:11 CEST

On Thu, 2004-06-17 at 12:31, Ben Collins-Sussman wrote:
> 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.

I don't think so: rpm -qa | grep db4

there is a db4-4.1.25-8 further down in the list, but I'm pretty sure
that svn is not using that (because the rpm wouldn't install until I had
the 4.2 version in place).

> > 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/

no, I didn't try that - if I restore that tar file to a different path
name on the same system and try it, should that work (that is, does it
care what path it is at)?

Scott Lawrence
Consulting Engineer
Pingtel Corp.   
+1.781.938.5306 x162
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 17 19:20:27 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.