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

Re: seemingly corrupt db?

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-11-21 19:56:00 CET

Bryan Donlan wrote:

>On 19 Nov 2004 20:13:42 -0600, kfogel@collab.net <kfogel@collab.net> wrote:
>
>
>>Geoff Smith <geoffrey.smith@nrl.navy.mil> writes:
>>
>>
>>>>Did someone maybe upgrade Berkeley DB shared libraries on that system,
>>>>after you installed Subversion?
>>>>
>>>>
>>>Not that I know of, unless I did it by mistake. I did do an OS
>>>update, but don't know if that updated the DB libs. Is there a good
>>>way to check the versions?
>>>
>>>
>>An OS upgrade will often upgrade BDB, yeah. You could look at
>>/usr/include/db.h (assuming that's where Berkeley's headers are) and
>>poke around for something like this:
>>
>> /*
>> * Berkeley DB version information.
>> */
>> #define DB_VERSION_MAJOR 4
>> #define DB_VERSION_MINOR 2
>> #define DB_VERSION_PATCH 50
>> #define DB_VERSION_STRING "Sleepycat Software: Berkeley DB 4.2.50: (November 20, 2003)"
>>
>>As for solutions: I'm not sure, but if you could compile a Subversion
>>statically against the old libs, you could run 'svnadmin dump' on the
>>repository, save the dumpfile, recreate the repository with a newly
>>compiled Subversion, and load it? I'm winging it here, though.
>>
>>
>
>I remember reading on these lists somewhere that you can delete the
>__db.* files and db_recover it, and it'll be accessible from the new
>version.
>
It will, but Subversion still has to be compiled against the new BDB.

>I'd do it on a copy though, and dump/reload after if it works.
>
>
If it works, you most likely don't need a dump/load. :-)

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 21 19:57:56 2004

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