OK, the svn dump + load into a new repository worked well; everything is
back up and running again.
I'll switch to the 1.1.x branch as soon as it is available of off fink,
and I'll keep regular dumps (after each commit) of my repository.
Fortunately, I'm the only person using this repository (I'm mostly using
this project as an excuse to learn subversion) so I don't need to worry
about hot dumps, etc.
Thanks,
Cem Karan
> -----Original Message-----
> From: Max Bowsher [mailto:maxb@ukf.net]
> Sent: Tuesday, November 02, 2004 4:52 AM
> To: Karan, Cem (Civ, ARL/CISD); users@subversion.tigris.org
> Subject: Re: extremely wedged repository
>
>
> Karan, Cem (Civ, ARL/CISD) wrote:
> > I've managed to wedge my repository to the point that I can't get
> > svnadmin recover to work, and the Berkley tools segfault
> just trying
> > to work on it. Here are the specs of what I've got, and what is
> > wedged:
> >
> > Running on Mac OS X 10.3.5 with all of the latest patches
> (last patch
> > update was 28 Oct 2004, which was the latest release).
> >
> > Using Subversion 1.0.9 (r11378) as installed by fink
> > (http://fink.sourceforge.net)
> >
> > When I try to use 'time svn recover', it claims that the
> recovery is
> > complete, and that the latest revision is 10 (which makes
> sense) but
> > it does the entire recovery in 0.140 seconds of user time;
> I'll admit,
> > I only have a couple hundred files, but that is a bit fast.
> >
> > When I do 'db_recover -c', I get the following:
> > db_recover: DB_LOGC->get: LSN 13/843898: invalid log record header
> > Segmentation fault
>
> Well, if the log files are somehow corrupt, I'd recommend
> making a *copy* of
> the repository, deleting the log files from the copy, and
> then running
> recovery. If that works, create a new empty repository, dump/load the
> history, copy across any hook scripts, and put the new
> repository back into
> service.
>
> You probably want to migrate to FSFS once you upgrade to
> 1.1.x - we've seen
> *far* too many of these mysterious problems with BDB on OS X.
>
> > When I go to my project directory, and run svn cleanup, everything
> > seems OK.
>
> Unsurprising, cleanup does not contact the repository.
>
> > But when I try to commit, I always get the following:
> >
> > Sending (a source file)
> > Adding (another source file)
> > Abort Trap
> >
> > There are only 2 other possible oddities in how I set up my
> > directories:
> > 1) I do use spaces in some of my names (E.g., I may have a path like
> > "foo/baz/bar bar") but this doesn't seem to have thrown it before.
> > 2) I'm running everything off of an encrypted disk image;
> I've checked
> > to make sure that there is enough room to do the commits,
> and there is.
> > Also, there didn't seem to be any problems before.
>
> Neither of the above seem likely to cause problems.
>
> > Any suggestions? Also, if this is going to a mailing list, I'm not
> > part of the list; you'll have to mail me directly.
>
> Max.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 3 17:09:42 2004