• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Subversion database corruption
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subversion database corruption


  • Subject: Subversion database corruption
  • From: Daniel Jalkut <email@hidden>
  • Date: Wed, 3 Aug 2005 13:24:22 -0400


*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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Subversion database corruption
      • From: Dave Camp <email@hidden>
    • Re: Subversion database corruption
      • From: Dave Rehring <email@hidden>
    • Re: Subversion database corruption
      • From: Markus Hitter <email@hidden>
    • Re: Subversion database corruption
      • From: Bill Bumgarner <email@hidden>
  • Prev by Date: Re: Subclass responsibility error
  • Next by Date: Re: Subversion database corruption
  • Previous by thread: Re: same function, different mangled names
  • Next by thread: Re: Subversion database corruption
  • Index(es):
    • Date
    • Thread