Another item to note about ' DB_RUNRECOVERY ',
I discovered after pounding my head against the wall.
i.e.
----------------------------------------
$ svnadmin recover /usr/local/svn/cgi
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
-----------------------------------------
I discovered one of the '__db' files in the 'db' directory didn't have 'g'
'w'rite permission (I have permissions based on groups via svn+ssh). I'm
not sure how it happened, since all the rest of the files were ok. Once I
did a 'g+w' on the file, the problem went away.
Any way to make that error message a little more 'informative', when it
happens?
Just 2 more cents to the issue,
:)
-Iain
On Tue, 27 Apr 2004, Ben Collins-Sussman wrote:
> On Tue, 2004-04-27 at 10:40, kfogel@collab.net wrote:
>
> > Next time, don't wipe out your existing repository and restore from a
> > backup. Instead, run database recovery on the existing repository:
> >
> > http://subversion.tigris.org/project_faq.html#wedged-repos
>
> Also, here's a FAQ about tracking down the cause of the wedging:
>
> http://subversion.tigris.org/project_faq.html#permissions
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 28 03:58:32 2004