I actually don't think Subversion is the culprit... unless for some
reason it failed to exit in the last commit and kept the database open
without flushing some of the changes. My hope in posting here is that
someone has come across a related problem on their own system and knows
enough about the database system to point me on the path that gets the
repository working again. The database folks know Berkeley DB, but not
how Subversion uses it.
To answer your question, the db_dump -r (or -R) do seem to restore the
database (at least temporarily), but it fails to restore the
repository. The fun part is that if I try to run svnadmin verify at the
end of the following command sequence, I get into a cycle; simply
trying to verify the repository (with an apparently recovered database)
causes the nodes table to become corrupted again. I can repair it,
sure, but it doesn't stay that way.
$ svnadmin verify ~/SVN_Documents/DB
* Verified revision 0.
* Verified revision 1.
svn: Checksum mismatch on rep '3':
svn: Berkeley DB error while closing 'nodes' database for filesystem
DB_RUNRECOVERY: Fatal error, run database recovery
$ db_verify nodes
db_verify: PANIC: fatal region error detected; run recovery
$ sudo db_recover -v
db_recover: Finding last valid log LSN: file: 3 offset 401252
db_recover: Recovery starting from 
db_recover: Recovery complete at Sun May 2 02:42:15 2004
db_recover: Maximum transaction ID 80000008 Recovery checkpoint
$ db_verify nodes
I've looked at the output of the db_dump command, and there's no way I
could edit it.... it's lots and lots of numbers that simply don't mean
anything to me. Is there any way to know which file is causing the
specific error (checksum mismatch) from svnadmin verify?
I'd be happy if I could even get some of the revisions out.
On May 2, 2004, at 1:34 AM, Branko Čibej wrote:
> Mark Slater wrote:
>> I posted this problem to the user's list, but heard only silence... I
>> also posted on the berkeley DB newsgroup and got an answer that,
>> while the command worked, failed to restore functionality to the
>> repository. So here goes...
>> A few days ago, I went to shut my computer off (MacOS X 10.3.3, Dual
>> G4)... after 10-20 minutes of being logged out, but not shut off, I
>> decided it needed help, so I pushed the restart button. I'm not sure
>> if that has anything to do with the problem though... it had been a
>> while since my last checkin for the day. Anyway, the next day, two
>> of my subversion repositories were corrupted. One was fixed with
>> svnadmin --recover. The other one seems to be much worse off.
> I don't see how Subversion can be the culprit here? This looks like an
> OS bug to me, not flushing file caches to disk or something.
>> Here's the question and answer from the Berkeley DB newsgroup:
> So, have you tried db_dump -r?
>> If there's anything else I can provide that will help determine what
>> the problem is, how to fix it, and maybe even what caused it, please
>> let me know.
> I don't think anyone here can help you. It doesn't look like the data
> corruption was caused by Subversion, but by the combination of you OS
> no flushing buffers and you turning off the power. I suggest you do
> what the BDB people proposed; db_dump -r, and if that doesn't help,
> then db_dump -R and edit the result -- although I'm not sure how...
> -- Brane
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun May 2 11:50:28 2004