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

Re: Catastrophic database recovery with db log files

From: Matthias Saou <thias_at_spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net>
Date: 2004-03-24 10:42:17 CET

Ben Collins-Sussman wrote :

> On Tue, 2004-03-23 at 09:12, Matthias Saou wrote:
> > I don't have a backup of the very latest content, but I do have all the
> > logfiles created ever since the repository was started, so I'd be really
> > interested in being able to "replay" all of those. Can anyone point me to
> > an explanation on how to do it?
> 1. Copy your whole repository, play with the copy.
> 2. Delete the 7 tables: nodes, revisions, representations, changes,
> strings, transactions, uuids
> 3. run 'db_recover -c -h /path/to/repos/db'
> (The -c is for 'catastrophic' recovery.)
> I believe this is what the BDB docs recommend.

This worked perfectly, thanks a lot!
Now, although I reinstalled db 4.1 without the NPTL (posixmutexes IIRC)
stuff, I still get my repository locked and unusable after trying large
commits, which is pretty annoying. I guess I'll try to recompile against
db 4.2 instead.

Thanks again for your help, it saved quite some work :-)


Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 1 (Yarrow) - Linux kernel 2.6.3-2.1.253
Load : 0.99 0.52 0.20
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 24 10:43:09 2004

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