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

Re: DB_RUNRECOVERY but recovery attempts do not work

From: Robert Feldt <Robert.Feldt_at_htu.se>
Date: 2004-09-27 09:22:43 CEST

Garrett Rooney wrote:

>> Thanks for your answer; that sounds reasonable. Is there some way to
>> find out which version that is or should any 4.x version work?
> Please keep questions CCing the list, so others can learn from the
> answers...
Oops, sorry.

> The answer to your question depends on your operating system. On most
> unix systems you can run 'ldd /path/to/svnadmin' to see what libraries
> it's linked against. Then you need to find the version of db_recover
> that came with that version of berkeley db (it'll probably be
> something like db4_recover or db42_recover). On Mac OS X you'd do
> 'otool -L /path/to/svnadmin', which should show you the same information.
Thanks but it didn't help running db_recover in the repository. I tested
several different versions of Berkeley DB without any luck. However,
after having copied the repository with a simple "copy -R repo t" I
could run "svnadmin recover t" on the copy and it was recovered with all
revisions intact. I then simply moved the temp reposotory back as the
original one and everything works nicely again. This same procedure
worked for several affected repositories.

I don't understand why this worked but I imagine it could have been due
to a file not being closed properly? Could also have something to do
with access rights on the repo.

Thanks for your help,

Robert Feldt

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 27 09:23:29 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.