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

Re: Corrupted repository

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-12-01 12:30:11 CET

On Tuesday 30 November 2004 08:37, Olivier Meunier wrote:
> Hi,
>
> I upgraded subversion from 1.0.2 to 1.0.8 yesterday. Everything was
> fine. Then I build subversion again (to have python2.2-subversion).
>
> Something went wrong but I don't know what. Now, the repository is
> broken.

Did you upgrade DB along the way? That seems to be the most common
problem people are running into. :/

[snip]
> I run "dump" (or verify) :
>
> $ svnadmin dump SVN > dump01
> * Dumped revision 0.
> svn: Berkeley DB error while reading node revision for filesystem
> SVN/db: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: Berkeley DB error while closing 'nodes' database for filesystem
> SVN/db: DB_RUNRECOVERY: Fatal error, run database recovery
>
> I tried to recover with db_recover, it seems to be fine too :
>
> $ db4.2_recover -evch SVN/db/
> db_recover: Finding last valid log LSN: file: 230 offset 721703
> db_recover: Recovery starting from [230][28]
> db_recover: Recovery complete at Tue Nov 30 14:30:33 2004
> db_recover: Maximum transaction ID 80101a12 Recovery checkpoint
> [230][721703]
>
> But when I run "dump", I got the same error message.

can you try doing an ldd /path/to/svn or ldd /path/to/mod_dav_svn if you
using http:// access? In general we see problems with "Invalid
Arguments", "Invalid Environments", etc. when people mix version. I'm
not sure what would cause you to fail to read the nodes table other than
a permissions issue... which it should've informed you of.

> My system is:
>
> Linux 2.6.9 (I tried on a 2.4.26 too)
> Subversion 1.0.8
> bdb 4.2.52
>
> I don't really know what to do, is there another way to dump the data
> (even manualy) ?

You can do it manually by using the db4.2_dump command. You will of
course need use db4.2_load to restore the table elsewhere. Just make
sure to get all of the relevant tables in the db directory (nodes,
representations, revisions, strings, transactions, and uuids).

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 1 12:32:26 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.