You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ævar Arnfjörð Bjarmason <av...@gmail.com> on 2004/10/15 00:09:21 UTC
Unable to recover repository with svnadmin recover.
I'm lost as to how this should be solved:
# whoami
root
# svnadmin recover /home/svnroot/
Repository lock acquired.
Please wait; recovering the repository may take some time...
svn: DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: Ignoring log file: /home/svnroot/db/log.0000000034: magic
number 88090400, not 40988
svn: bdb: Invalid log file: log.0000000034: Invalid argument
svn: bdb: PANIC: Invalid argument
svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: fatal region error detected; run recovery
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Unable to recover repository with svnadmin recover.
Posted by Ævar Arnfjörð Bjarmason <av...@gmail.com>.
Yes in fact it had, i was trying to recover a repository created on a
ppc machine on an x86 machine, as soon as i moved it back to the ppc
machine everything worked.
I presume i'll have to do such moves via dump/load in the future?
On Fri, 15 Oct 2004 09:06:22 +0100, Max Bowsher <ma...@ukf.net> wrote:
> Ævar Arnfjörð Bjarmason wrote:
>
>
> > I'm lost as to how this should be solved:
> >
> > # whoami
> > root
> > # svnadmin recover /home/svnroot/
> > Repository lock acquired.
> > Please wait; recovering the repository may take some time...
> > svn: DB_RUNRECOVERY: Fatal error, run database recovery
> > svn: bdb: Ignoring log file: /home/svnroot/db/log.0000000034: magic
> > number 88090400, not 40988
> > svn: bdb: Invalid log file: log.0000000034: Invalid argument
> > svn: bdb: PANIC: Invalid argument
> > svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> > svn: bdb: fatal region error detected; run recovery
>
> The magic number mismatch indicates that the log file was created on a
> big-endian machine, and is now being read on a little-endian machine, or
> vice versa.
>
> Has the respository just been copied from one kind of computer to another?
>
> Max.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Unable to recover repository with svnadmin recover.
Posted by Max Bowsher <ma...@ukf.net>.
Ævar Arnfjörð Bjarmason wrote:
> I'm lost as to how this should be solved:
>
> # whoami
> root
> # svnadmin recover /home/svnroot/
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: Ignoring log file: /home/svnroot/db/log.0000000034: magic
> number 88090400, not 40988
> svn: bdb: Invalid log file: log.0000000034: Invalid argument
> svn: bdb: PANIC: Invalid argument
> svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: fatal region error detected; run recovery
The magic number mismatch indicates that the log file was created on a
big-endian machine, and is now being read on a little-endian machine, or
vice versa.
Has the respository just been copied from one kind of computer to another?
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org