hello

this was really a subversion problem that i now consider a berkekley DB
issue

our repository is somehow corrupted.

so i ran

$ db_recover.exe -c -v -h D:\path\to\repos\db

which produces:
Finding last valid log LSN: file: 9779 offset 301002
Recovery starting from [9779][28]
Recovery complete at Thu Feb 16 23:54:26 2006
Maximum transaction ID 80a57a38 Recovery checkpoint [9779][301002]


that looked fine i thougt but when i subsequently access the database
(via subversion/apache) i get this error

Berkeley DB error for filesystem D:\path\to\repos\db while moving
cursor:
DB_RUNRECOVERY: Fatal error, run database recovery [500, #160029]
(20014)Error string not specified yet: Berkeley DB error for filesystem
D:\path\to\repos\db while closing 'nodes' database:
DB_RUNRECOVERY: Fatal error, run database recovery


can anyone explain how a complete DB recovery (with the -c flag )
doesn't work ?


so i tried
$ db_verify.exe -D:\path\to\repos\db\strings

which produces a lot of lines like this:
....
db_verify: Page 42293: btree or recno page is of inappropriate type 0
db_verify: Page 42293: totally zeroed page
db_verify: Page 43785: btree or recno page is of inappropriate type 0
db_verify: Page 43785: totally zeroed page
db_verify: Page 45017: btree or recno page is of inappropriate type 0
db_verify: Page 45017: totally zeroed page
db_verify: Page 352: unterminated leaf chain
db_verify: Page 538940: non-invalid page 538939 on free list
db_verify: D:\path\to\repos\db\strings: DB_VERIFY_BAD: Database
verification failed


i don't undetstand these messages, but i rekon they are not good news.
can someone point me in the right direction so we can recover our
repository

btw. i am infact to use some of the subversion admin tools after the
above recovery procedure, so i can for instance list dead
tranasactions, and see info regarding a specfic subversion revision
(though only on the root directory)

thanks
../a

Alan,

Yes, your database is corrupted. Your action of running db_recover is
not appropriate to restoring corrupted databases. db_recover MUST be
run any time your application or system crashes or exits abnormally.
It cannot do anything to repair a dammaged database. We see problems
from time to time in Subersion installations because there is no
controling process to coordinate when it is necessary to run recovery.

We have addressed this problem in our latest release of Berkeley DB
v4.4 and have worked with CollabNet to integrate the solution:
http://sleepycat.com/news/releases/060207.html

At this point you will need to restore your database from back up or
rebuild it. You can extract your data using the db_dump utility and
the -r flag which will attempt to ignore problems in the physical
structure of the database. Please see:
http://www.sleepycat.com/docs/utility/db_dump.html

Michael Ubell
Sleepycat Software.