• 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
Re: Subversion database corruption
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subversion database corruption


  • Subject: Re: Subversion database corruption
  • From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
  • Date: Wed, 3 Aug 2005 14:44:36 -0400
  • Thread-topic: Subversion database corruption

> *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?

1) Don't use the BDB backend!  My average corruption rate was 3 times/week using  the BDB backend.  I switched to FSFS and have had 0 problems since.

2) Subscribe to the SVN mailing list; there are a lot of us out there and we can help you out. http://subversion.tigris.org/servlets/ProjectMailingListList

The next question is how to save your repository.  First off, do you need to?  I mean, is the data in there vital, or was it just an experiment to see how things work?  If the former, talk to the guys on the list, I know that they have a few tricks where they can modify the database, and then you can dump out its contents to move it to a new repository.

By the way, what version of subversion are you using?  And how did you install it (Fink, built the sources yourself, etc.)?

Thanks,
Cem Karan

<<winmail.dat>>

 _______________________________________________
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

  • Prev by Date: Re: At a loss with cross development
  • Next by Date: Building apps to certain locations
  • Previous by thread: Re: Subversion database corruption
  • Next by thread: Building apps to certain locations
  • Index(es):
    • Date
    • Thread