You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Bastian Ebeling <ba...@hsu-hamburg.de> on 2006/02/08 07:25:33 UTC
Big problem with my SVN-repository
Hello support,
i have a problem with my repository.
Here is, what I reached with the tools after reading the hints from your
page:
(I also posted it to comp.databases.berkeley-db but now answer occured)
Hello newsgroup,
I have an uncomfortable problem: About 4 weeks ago our RAID-4-Array
degraded and after our admin regocnized that one hard disk failed. The
admin did his best to get the data back - and it nearly worked. Now I
have one remaining problem with my SVN-repository.
It is not working now because of an internal problem (which surely was
produced by that data reconstructing and so on).
I tried svnadmin verify and recover (which should equal the command
from db_recover and so on), and I got messages, which tell me, that the
database is not okay, and that I should start recover - which is
extremely helpful when one is already running recover...
Okay, here are the results:
>>> SNIP from console:
svnadmin recover .
svn: Can't open file 'format': Datei oder Verzeichnis nicht gefunden
gammaray:/home/ebeling# svnadmin recover mySVNROOT/
Exklusiven Zugriff auf das Projektarchiv erlangt
Bitte warten, die Wiederherstellung des Projektarchivs kann einige Zeit
dauern...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: Ignoring log file: mySVNROOT/db/log.0000000005: magic number
20646150, not 40988
svn: bdb: Invalid log file: log.0000000005: Das Argument ist
ung?\252ltig
svn: bdb: PANIC: Das Argument ist ung?\252ltig
svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
<<< END SNIP
if I try it with native db tools it looks like this:
>>> SBUO from console:
db4.2_recover -c
db_recover: Ignoring log file: log.0000000005: magic number 20646150,
not 40988
db_recover: Invalid log file: log.0000000005: Invalid argument
db_recover: PANIC: Invalid argument
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
recovery
<<< END SNIP
Okay, I'm sorry, I do not exactly know which DB-Version was used - it
was created with tortoise-svn.
I would be very happy if anyone here could help.
Thanks in advance,
Bastian Ebeling
It would be glad, if you can help me.
Greetings, Bastian Ebeling
--
==================================
Dipl.-Ing. Bastian Ebeling
Wissenschaftlicher Assistent
Fachbereich Maschinenbau
Professur für Mathematik
Telefon +49 (0) 40 6541-3574
Telefax +49 (0) 40 6541-2690
Raum 1229
Helmut-Schmidt-Universität
Universität der Bundeswehr Hamburg
Holstenhofweg 85
22043 Hamburg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
AW: Big problem with my SVN-repository
Posted by Bastian Ebeling <ba...@hsu-hamburg.de>.
Hello Dave,
thanks for your fast reaction. Yes, I tried before - and now I tried again
to show you the messages:
COPY FROM CONSOLE--------------->
:~# svnadmin dump /home/ebeling/mySVNROOT/
svn: Berkeley DB error while opening environment for filesystem
/home/ebeling/my
SVNROOT/db:
DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: Ignoring log file: /home/ebeling/mySVNROOT/db/log.0000000005:
magic nu
mber 20646150, not 40988
svn: bdb: Invalid log file: log.0000000005: Das Argument ist ung?\252ltig
svn: bdb: PANIC: Das Argument ist ung?\252ltig
svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
<--------------------------------
It would be great if you can give me any hint what to do. I even tried a
dump and/or repair with those native bdb tools.
Thanks again and in advance,
Bastian Ebeling
-----Ursprüngliche Nachricht-----
Von: Dave Camp [mailto:dave@thinbits.com]
Gesendet: Mittwoch, 8. Februar 2006 17:03
An: Bastian Ebeling
Cc: users@subversion.tigris.org
Betreff: Re: Big problem with my SVN-repository
Have you tried performing a svnadmin dump? Sometimes that works even
if recover doesn't.
Once you get to a dumpable state, you should stop using BDB and move
your repository to FSFS which is the default type now and does not
have those problems.
Dave
On Feb 7, 2006, at 11:25 PM, Bastian Ebeling wrote:
> Hello support,
>
> i have a problem with my repository.
> Here is, what I reached with the tools after reading the hints from
> your
> page:
>
> (I also posted it to comp.databases.berkeley-db but now answer
> occured)
> Hello newsgroup,
>
> I have an uncomfortable problem: About 4 weeks ago our RAID-4-Array
> degraded and after our admin regocnized that one hard disk failed. The
> admin did his best to get the data back - and it nearly worked. Now I
> have one remaining problem with my SVN-repository.
> It is not working now because of an internal problem (which surely was
> produced by that data reconstructing and so on).
> I tried svnadmin verify and recover (which should equal the command
> from db_recover and so on), and I got messages, which tell me, that
> the
> database is not okay, and that I should start recover - which is
> extremely helpful when one is already running recover...
> Okay, here are the results:
>
>>>> SNIP from console:
>
> svnadmin recover .
> svn: Can't open file 'format': Datei oder Verzeichnis nicht gefunden
> gammaray:/home/ebeling# svnadmin recover mySVNROOT/
> Exklusiven Zugriff auf das Projektarchiv erlangt
> Bitte warten, die Wiederherstellung des Projektarchivs kann einige
> Zeit
> dauern...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: Ignoring log file: mySVNROOT/db/log.0000000005: magic number
> 20646150, not 40988
> svn: bdb: Invalid log file: log.0000000005: Das Argument ist
> ung?\252ltig
> svn: bdb: PANIC: Das Argument ist ung?\252ltig
> svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> <<< END SNIP
>
> if I try it with native db tools it looks like this:
>
>>>> SBUO from console:
>
> db4.2_recover -c
> db_recover: Ignoring log file: log.0000000005: magic number 20646150,
> not 40988
> db_recover: Invalid log file: log.0000000005: Invalid argument
> db_recover: PANIC: Invalid argument
> db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
> recovery
> <<< END SNIP
>
> Okay, I'm sorry, I do not exactly know which DB-Version was used - it
> was created with tortoise-svn.
>
> I would be very happy if anyone here could help.
>
> Thanks in advance,
>
> Bastian Ebeling
>
>
>
> It would be glad, if you can help me.
>
> Greetings, Bastian Ebeling
>
>
> --
> ==================================
> Dipl.-Ing. Bastian Ebeling
> Wissenschaftlicher Assistent
> Fachbereich Maschinenbau
> Professur für Mathematik
> Telefon +49 (0) 40 6541-3574
> Telefax +49 (0) 40 6541-2690
> Raum 1229
>
> Helmut-Schmidt-Universität
> Universität der Bundeswehr Hamburg
> Holstenhofweg 85
> 22043 Hamburg
>
>
> ---------------------------------------------------------------------
> 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
Re: Big problem with my SVN-repository
Posted by Dave Camp <da...@thinbits.com>.
Have you tried performing a svnadmin dump? Sometimes that works even
if recover doesn't.
Once you get to a dumpable state, you should stop using BDB and move
your repository to FSFS which is the default type now and does not
have those problems.
Dave
On Feb 7, 2006, at 11:25 PM, Bastian Ebeling wrote:
> Hello support,
>
> i have a problem with my repository.
> Here is, what I reached with the tools after reading the hints from
> your
> page:
>
> (I also posted it to comp.databases.berkeley-db but now answer
> occured)
> Hello newsgroup,
>
> I have an uncomfortable problem: About 4 weeks ago our RAID-4-Array
> degraded and after our admin regocnized that one hard disk failed. The
> admin did his best to get the data back - and it nearly worked. Now I
> have one remaining problem with my SVN-repository.
> It is not working now because of an internal problem (which surely was
> produced by that data reconstructing and so on).
> I tried svnadmin verify and recover (which should equal the command
> from db_recover and so on), and I got messages, which tell me, that
> the
> database is not okay, and that I should start recover - which is
> extremely helpful when one is already running recover...
> Okay, here are the results:
>
>>>> SNIP from console:
>
> svnadmin recover .
> svn: Can't open file 'format': Datei oder Verzeichnis nicht gefunden
> gammaray:/home/ebeling# svnadmin recover mySVNROOT/
> Exklusiven Zugriff auf das Projektarchiv erlangt
> Bitte warten, die Wiederherstellung des Projektarchivs kann einige
> Zeit
> dauern...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: Ignoring log file: mySVNROOT/db/log.0000000005: magic number
> 20646150, not 40988
> svn: bdb: Invalid log file: log.0000000005: Das Argument ist
> ung?\252ltig
> svn: bdb: PANIC: Das Argument ist ung?\252ltig
> svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> <<< END SNIP
>
> if I try it with native db tools it looks like this:
>
>>>> SBUO from console:
>
> db4.2_recover -c
> db_recover: Ignoring log file: log.0000000005: magic number 20646150,
> not 40988
> db_recover: Invalid log file: log.0000000005: Invalid argument
> db_recover: PANIC: Invalid argument
> db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database
> recovery
> <<< END SNIP
>
> Okay, I'm sorry, I do not exactly know which DB-Version was used - it
> was created with tortoise-svn.
>
> I would be very happy if anyone here could help.
>
> Thanks in advance,
>
> Bastian Ebeling
>
>
>
> It would be glad, if you can help me.
>
> Greetings, Bastian Ebeling
>
>
> --
> ==================================
> Dipl.-Ing. Bastian Ebeling
> Wissenschaftlicher Assistent
> Fachbereich Maschinenbau
> Professur für Mathematik
> Telefon +49 (0) 40 6541-3574
> Telefax +49 (0) 40 6541-2690
> Raum 1229
>
> Helmut-Schmidt-Universität
> Universität der Bundeswehr Hamburg
> Holstenhofweg 85
> 22043 Hamburg
>
>
> ---------------------------------------------------------------------
> 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