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

RE: DB Corruption

From: Terry Smith <terry_at_tsmith.com>
Date: 2005-07-13 04:01:55 CEST

I have not had a chance to work with Max's proposed solution; I am
unwilling to tackle it until I have a block of uninteruppted time so
that I do not get in a hurry and miss a simple point.

But in reading Branko's email, I realized I missed a point that might be
relevent.

First, to Branko's question: This is a first time subversion install so
no upgradeshave been done.

Second, I failed to mention that I use TortiseSVN. I doubt this is
important. I assume it just generates command strings and is no worse
(much better) than my typing would be.

In any event, I expect to dig in and try a restore this weekend and will
reply with final resolution.

Thanks for the quick support.

Terry Smith

-----Original Message-----
From: Branko Cibej [mailto:brane@xbc.nu]
Sent: Monday, July 11, 2005 6:56 AM
To: Terry Smith
Cc: users@subversion.tigris.org
Subject: Re: DB Corruption

Terry Smith wrote:

> Hi, I am having a problem with corruption. This looks like another
> flavor of a regular problem.
>
> First I saw this:
> -------
>
> C:\Documents and Settings\Terry>svnadmin recover
> c:/Subversion/repository Repository lock acquired. Please wait;
> recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: DB_ENV->log_flush: LSN of 99/206498 past current end-of-log
> of 99/1841
> 50
> svn: bdb: Database environment corrupt; the wrong log files may have
> been remove
> d or incompatible database files imported from another environment
> svn: bdb: strings: unable to flush page: 0
> svn: bdb: txn_checkpoint: failed to flush the buffer cache Invalid
> argument
> svn: bdb: PANIC: Invalid argument
> svn: bdb: PANIC: fatal region error detected; run recovery
> svn: bdb: PANIC: fatal region error detected; run recovery
> (repeated many times)

You don't say which version of Subversion you're using. DId you, by any
chance, recently upgrade from 1.1.x to 1.2.x? Becaues here's what the
1.2.0 README.txt says abou upgrading:

***** IMPORTANT *** Upgrading from 1.1.x to 1.2.x *** IMPORTANT *****

In this release, we've upgraded BerkeleyDB from version 4.2.52 to
4.3.27. If you are currently using Subversion 1.1.x as a server on
Windows with BerkeleyDB, use the following steps to upgrade your
repositories:

  -- Make sure nobody is using the repository (stop Apache/svnserve,
     restrict access via file://).
  -- For each repository, using the old (1.1.x) binaries:
     -- Run "svnadmin recover <repos-dir>";
     -- Create a backup of the repository;
     -- Run "svnadmin list-unused-dblogs <repos-dir>"
        and remove the listed files;
     -- Delete all the "<repos-dir>\db\__db.00?" files.
  -- Upgrade Subversion.

Once again, this is only necessary for repositories based on BDB. You do
NOT have to dump/reload your repositories.

*********************************************************************

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 13 04:03:29 2005

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