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

Corrupted repository

From: Olivier Meunier <omeunier_at_eyrolles.com>
Date: 2004-11-30 14:37:01 CET


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.

When I run "recover" :

$ svnadmin recover SVN
Please wait; recovering the repository may take some time...

Recovery completed.
The latest repos revision is 1037.

It seems to be fine but...

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

But when I run "dump", I got the same error message.

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) ?


Olivier Meunier
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 30 14:38:52 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.