You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Todd Chapman <to...@chaka.net> on 2005/10/26 20:20:17 UTC
Is my repository hosed?
This is a follow on to the message I posted a few days ago, which nobody answered.
Here is the original message:
==================
My Mac mini has a power outage. Doing a recover seems to work
but I have strange problems. The problem is that I can checkout
at top level repository directory, but if I try to check out
a subdirectory I get database corruption. Any Ideas?
Thanks!
mini:~ chapman$ ps aux | grep svn
chapman 715 0.0 0.1 31684 460 ?? Ss 3:09PM 0:00.01 svnserve -d -r
+/Users/chapman/svn/public
chapman 727 0.0 0.0 27800 4 p2 R+ 3:14PM 0:00.00 grep svn
mini:~ chapman$ kill 715
mini:~ chapman$ svnadmin recover svn/public_repository/
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 203.
mini:~ chapman$ svnserve -d -r /Users/chapman/svn/public_repository/
mini:~ chapman$ rm -rf junk*
mini:~ chapman$ svn co -q svn://localhost/RTx-RightsMatrix/ junk
mini:~ chapman$ svn co -q svn://localhost/RTx-RightsMatrix/branches/ junk2
svn: Berkeley DB error while appending string for filesystem /Users/chapman/svn/public_repository/db:
DB_RUNRECOVERY: Fatal error, run database recovery
mini:~ chapman$ svn --version
svn, version 1.0.6 (r10360)
compiled Aug 24 2004, 15:57:25
=====================
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?
Thanks!
-Todd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Is my repository hosed?
Posted by Todd Chapman <to...@chaka.net>.
On Wed, Oct 26, 2005 at 03:34:23PM -0700, David Ripton wrote:
> On 2005.10.26 17:02:13 -0400, Todd Chapman wrote:
> > 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.
>
> Yeah.
>
> > I'll also try the Sleepycat tool to see what it uncovers.
>
> Since you had to dump and load anyway, why not just switch to fsfs?
Good idea. And, since that is the now the default, I did.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Is my repository hosed?
Posted by David Ripton <dr...@ripton.net>.
On 2005.10.26 17:02:13 -0400, Todd Chapman wrote:
> 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.
Yeah.
> I'll also try the Sleepycat tool to see what it uncovers.
Since you had to dump and load anyway, why not just switch to fsfs?
--
David Ripton dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Is my repository hosed?
Posted by Todd Chapman <to...@chaka.net>.
On Wed, Oct 26, 2005 at 04:20:37PM -0500, Joshua Varner wrote:
> On 10/26/05, Todd Chapman <to...@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
Re: Is my repository hosed?
Posted by Joshua Varner <jl...@gmail.com>.
On 10/26/05, Todd Chapman <to...@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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org