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

Re: Database recovery problem

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-08-23 19:42:17 CEST

Damien Tougas wrote:
> Hello,
> On Aug 23, 2004, at 1:02 PM, Max Bowsher wrote:
>> If you are lucky, then making a copy of your repository and removing
>> (from a COPY), __db.*, and then trying "svnadmin recover repospath",
>> and then if that doesn't work "db_recover -vec" (executed from the db
>> subdirectory of the copy of the repository), will fix things.
> It does not appear that I have any files that begin with __DB.*, is
> that normal?

Very unusual. Whilst it is in certain circumstances ok to delete these
files, they should be re-created at the first attempt to access the
repository thereafter. In the db subdirectory of the repository, with names
__db.001 __db.002 __db.003 __db.004 __db.005 .

>> If not, try the same again, this time try removing both __db.* and
>> log.* . If you now have a functioning repository don't put it back
>> into service - "svnadmin dump" it, and load the dump into a new
>> repository.
> Removing the log.* files seemed to fix the database restore, I was able
> to do it using the svnadmin utility. As per your recommendation, I did
> a dump on the repaired repository and then a load on a new repository.
> Thank you very much for your help!
> Have I lost anything be removing those log files? (there were two of
> them, one was 1.0 Mb, and the other was 6.3 Kb).

After a successful dump/load, very likely you have lost nothing - just check
if the total number of revisions is correct. Each revision should be either
completely intact or completely missing.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 23 19:43:04 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.