Corrupted DB file which is unrecoverable using svnadmin or db_recover

[Douglas Rudd <dr...@drudd.com>]

During a recent commit I started receiving the error:
svn: Berkeley DB error while opening 'revisions' table for filesystem
/home/svnroot/db:

and I get the same error if I attempt svnadmin recover:
# svnadmin recover /home/svnroot/
Acquiring exclusive lock on repository db.
Recovery is running, please stand by...
Recovery completed.
svn: Berkeley DB error
svn: Berkeley DB error while opening 'revisions' table for filesystem
/home/svnroot/db:
Invalid argument

I have tried
# db_recover -c -v
db_recover: Finding last valid log LSN: file: 245 offset 842850
db_recover: Recovery starting from [1][28]
db_recover: Recovery complete at Wed Jul  4 17:37:14 2007
db_recover: Maximum transaction ID 8001f100 Recovery checkpoint [245][842850]
db_recover: Recovery complete at Wed Jul  4 17:37:14 2007
db_recover: Maximum transaction id 80000000 Recovery checkpoint [245][842850]

but it doesn't seem to be finding any corruption.  I have also tried
dumping the revisions table and then loading it, but that didn't fix
the issue.

Admittedly I'm running an out of date version of subversion:
# svn --version
svn, version 0.32.1 (r7497)
  compiled Jun  9 2004, 09:33:15

If anyone can help me repair the database just enough to dump the data
and migrate to a newer version of subversion I'd be very grateful, as
I'd hate to lose the revision history (only have an old backup
too...).

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org