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

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-23 16:12:36 CET


About the log.0000* files, the svnbook states :

"Without some sort of automatic log file removal in place, log files will
 accumulate as you use your repository. This is actually somewhat of a
 feature of the database system___you should be able to recreate your entire
 database using nothing but the log files, so these files can be useful for
 catastrophic database recovery"

Well, I've been bitten by the Fedora Core 1 db 4.1 NTPL problem, and have
a corrupt "copies" file in my repository :

# svnadmin recover /svn
Please wait; recovering the repository may take some time...
Recovery completed.
svn: Berkeley DB error while opening 'copies' table for filesystem /svn/db:
Invalid argument

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?


Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 1 (Yarrow) - Linux kernel 2.6.3-2.1.253
Load : 1.57 1.02 0.89
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 23 16:13:38 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.