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

Re: BDB version changed in win32 binaries ? (Was Re: Subversion 1.2.0 Release Candidate 2 released.)

From: Kyle Kline <kyle.kline_at_gmail.com>
Date: 2005-04-29 19:12:20 CEST

This worked for me as well, and solved the issue. Thank you, Max!

Should this be added to the FAQ/known 'issues'/or release notes since
a lot of users who upgrade to 1.2 final will be asking the same
question ... ?

-Kyle

On 4/29/05, François Beausoleil <fbeausoleil@ftml.net> wrote:
>
>
> Max Bowsher said the following on 2005-04-29 08:44:
> > Actually, it does!
> >
> > I recall seeing this combination of errors before.
> >
> > What you need to do is:
> >
> > $ svnadmin recover repos
> > # this will error like it does above, but that is ok.
> > $ svnlook youngest repos
> > # this should work
> >
> > To fully follow the Berkeley DB guidelines, you *should* be additionally
> > be running recovery with the *old* version of BDB first, too, but I
> > appreciate this may be hard to do, and _seems_ to be unnecessary
> > providing the database was in a good state before the version change.
>
> Okay, I ran just that:
>
> $ "C:\Program Files\Subversion"\bin\svnadmin recover repos
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 3364.
>
> $ svnadmin recover repos
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> svnadmin: DB_RUNRECOVERY: Fatal error, run database recovery
> svnadmin: bdb: Program version 4.3 doesn't match environment version
> svnadmin: bdb: Skipping log file repos/db\log.0000002942: historic log
> version 8
> svnadmin: bdb: repos/db\log.0000002943: log file open failed: No such
> file or directory
> svnadmin: bdb: PANIC: No such file or directory
> svnadmin: bdb: DB_ENV->log_put: 2943: DB_RUNRECOVERY: Fatal error, run
> database recovery
>
> $ svnlook youngest repos
> 3364
>
> And now I have 1.2.0 binaries operating my repository. Great !
>
> Although, the error messages aren't very nice to look at... Is there
> anything that can be done about that ?
>
> > Additionally, if you are operating any incremental backup scheme based
> > on BDB logfiles, you should immediately perform a *full* backup after
> > the version upgrade above has been completed.
>
> Oh, I'm using incremental BZ2 dumps, so no problem about that.
>
> Thanks for the help !
> François
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 29 19:19:10 2005

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.