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.
Here are some of the error messages I'm getting:
$ svnadmin verify ./RD
* Verified revision 0.
* Verified revision 1.
svn: Checksum mismatch on rep 'u':
expected: 34ebc892de3302284606f110c3e573ca
actual: 13796ec7e50d0e0a50048df550db0758
$ sudo svnadmin recover ./RD
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
$ db_verify nodes
db_verify: Page 2: unreferenced page
db_verify: Page 3: unreferenced page
db_verify: DB->verify: nodes: DB_VERIFY_BAD: Database verification
failed
$ db_verify representations db_verify: Page 2: unreferenced page
db_verify: Page 3: unreferenced page
db_verify: DB->verify: representations: DB_VERIFY_BAD: Database
verification failed
$ db_verify strings
db_verify: Page 58: first page in overflow chain has a prev_pgno 57
db_verify: Page 111: overflow item incomplete
db_verify: Page 21: incorrect next_pgno 61 found in leaf chain (should
be 91)
db_verify: Page 58: overflow page linked twice from leaf or data page
db_verify: Page 38: overflow page linked twice from leaf or data page
db_verify: Page 54: overflow page of invalid type 5
db_verify: Page 55: overflow page linked twice from leaf or data page
db_verify: DB->verify: strings: DB_VERIFY_BAD: Database verification
failed
$ sudo db_recover
db_recover: Log sequence error: page LSN 2 322820; previous LSN 2 885276
db_recover: Recovery function for LSN 2 887886 failed on forward pass
db_recover: PANIC: Invalid argument
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: PANIC: fatal region error detected; run recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
recovery
Here's the question and answer from the Berkeley DB newsgroup:
http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&oe=UTF
-8&threadm=adecb6f.0404291101.4380b1c9%40posting.google.com&prev=/
groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF
-8%26group%3Dcomp.databases.berkeley-db
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.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 2 05:04:38 2004