Try to create an FSFS repository (if you created a new one using 1.2.3,
then you should have this by default) as it is more stable that the
database backend.
Good luck,
Cem Karan
-----Original Message-----
From: Todd Chapman [mailto:todd@chaka.net]
Sent: Wednesday, October 26, 2005 5:02 PM
To: Joshua Varner
Cc: users@subversion.tigris.org
Subject: Re: Is my repository hosed?
On Wed, Oct 26, 2005 at 04:20:37PM -0500, Joshua Varner wrote:
> On 10/26/05, Todd Chapman <todd@chaka.net> wrote:
> > This is a follow on to the message I posted a few days ago, which
nobody answered.
> >
> >
> > Since then I have upgraded to svn 1.2.3 and I have the same problem.
> >
> > Is recover not really doing it's job? Do I need to rebuild my
repository?
> >
> Try running svnadmin verify
> http://svnbook.red-bean.com/nightly/en/svn.ref.svnadmin.c.verify.html
>
> There is also a db_recover tool or something like that from Sleepycat,
> that checks the database differently than svnadmin recover, I just
> can't find it right now.
> Josh
Thanks for the tip. I already did a dump/load and that seemed to fix
my problem. However I did still have my old repository around so I
did a verify and it was ok.
It is disappointing that a power outage on a quiet repository (I am
the only user) would hose the repo. and that recover reports success
when it obviously didn't do the job.
I'll also try the Sleepycat tool to see what it uncovers.
Thanks again for you response.
-Todd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 27 14:07:30 2005