[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: <ark-d_at_betasystems.com>
Date: 2004-10-27 17:25:23 CEST

> if BDB continues to create problems for you, you can try
> switching to an FSFS repository instead.

is there any scripts/tools which could convert BDB repositories to FSFS?

my problem is that I have converted some CVS projects to SVN with the
latest
cvs2svn tool. The repos's will be generated in bdb and due to the known bdb
problems,
I have to move to FSFS. I've tryed to --dump-only my CVS repos/proj and
load it to the underlying projects
within a single repository, so far I can see the dump / load approach is
only possible
for one project. I would like to have one single repository with multiple
projects within,
due to the fact that most of our projects are related and should share
libraries.

--> what's the best way for such a scenario?

thanks in advance,
arash

                                                                           
             Ben
             Collins-Sussman
             <sussman@collab.n To
             et> Lukas Cerman
                                       <lukas.cerman@altap.cz>
             27.10.2004 16:13 cc
                                       users@subversion.tigris.org
                                                                   Subject
                                       Re: serious trouble
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           

On Oct 27, 2004, at 7:07 AM, Lukas Cerman wrote:

> Hi all!
>
> We are unable to recover our repository. The repository is inaccesible
> since one user's commit has crashed. We tried use svnadmin recover --
> as described in manual -- but we get allways this response:
>
> raid:/tmp# svnadmin recover /tmp/all
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery

Try using the db_recover utility in catastrophic mode (-c):

    $ db_recover -vech /tmp/all/db/

>
> 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?

See the FAQ:
http://subversion.tigris.org/project_faq.html#stuck-bdb-repos

>
> Any suggestion?
>
> We have version:
> svnadmin, version 1.0.8 (r11084)
> compiled Sep 27 2004, 01:09:34
>

Upgrade to 1.1. 'svnadmin recover' gives better error messages in 1.1,
and also, if BDB continues to create problems for you, you can try
switching to an FSFS repository instead.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 27 17:28:31 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.