[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: serious trouble

From: Jacob Atzen <jacob_at_aub.dk>
Date: 2004-10-27 19:20:21 CEST

On Wed, Oct 27, 2004 at 02:07:45PM +0200, Lukas Cerman wrote:
> raid:/tmp# svnadmin recover /tmp/all
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
>
> What should we do? We tried to copy repository to /tmp and run recover
> as root -- which has all priveleges, don't has? -- with this result.
>
> We shifted from CVS to SVN one month ago and were very pleasured. But we
> are concerned on data consistency and this make us affraid. What should
> we do to recover our repository and to prevent it happens again?
>
> Any suggestion?

You aren't by any chance using multiple access methods?

Check the permissions of the files in the db catalog of the repository.
All should be read- and writable by everyone who needs to read or write
to the repository.

And if you're worried about data consistency (which you shouldn't be as
consistency is perhaps the number one priority of the subversion devs)
make sure to backup after every commit. It's quite easy to setup with a
post-commit hook.

-- 
Cheers,
- Jacob Atzen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 27 19:20:48 2004

This is an archived mail posted to the Subversion Users mailing list.