Re: Subversion database corruption
Re: Subversion database corruption
- Subject: Re: Subversion database corruption
- From: Dave Camp <email@hidden>
- Date: Wed, 3 Aug 2005 14:06:16 -0700
The root of your problems, sadly, is that you are using Berkeley DB
for the backend. I know this because I lost 7 of them in one day.
Consensus is that people really need to use the fsfs backend. Even
the Subversion developers have admitted that they are using bdb
incorrectly and it is a source of problems.
Move off bdb as fast as you can. It's pretty easy to do. Email me off-
list and I might be able to give you some tips if needed.
Dave
On Aug 3, 2005, at 10:24 AM, Daniel Jalkut wrote:
*sigh* I'm starting to really wonder why I switched to svn. I
switched because I was starting a new repository, and I thought I
might as well start over with "what everybody is raving about."
Mostly this has been an exercise in working around Xcode's
lackluster svn integration. Annoying, but manageable.
Today my svn repository stopped working altogether. Cryptic errors
about "run recover" led me to google results that advised me to use
the Berkeley DB recovery functions. My best stab at doing so
yields this:
iBook> db4_recover -c -v -h /Users/daniel/Sources/SVNROOT/db/
db_recover: Finding last valid log LSN: file: 18 offset 361313
db_recover: Recovery starting from [17][28]
db_recover: Log sequence error: page LSN 18 66912; previous LSN 18
360678
db_recover: Recovery function for LSN 18 360744 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: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
recovery
I guess this *could* have just as easily happened with cvs. But
over the past five years, it never did. Now it's looking like I'll
have to start over from my latest checkout. Anybody care to
dissuade me from running back to cvs's arms?
Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40criticalpath.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden