You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Vidar <vl...@ez.no> on 2005/03/17 14:17:40 UTC
Svn repository (berkely) has "really" crashed, input on how to recover?
Hi
I have a svn repository (0.36.0-8282) that has crashed. Doing a "svnadmin
recover" apparently fixed the problem. However, if I then try to dump the
repository (or do checkout, commit etc..) the repository instantly crashes
again. So I guess someting is really messed up in the db structure and that
"recover" is unable to fix.
Since I am unable to dump the repository, I am also unable to upgrade it.
So, does anyone have some input on what to try in order to get the repository
back online again (except using a previous backup) ?
Best regards,
Vidar
--
vidar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Svn repository (berkely) has "really" crashed, input on how to recover?
Posted by Vidar <vl...@ez.no>.
Hi
Some more information....
I browsed through the mail archive and so that maybe dumping the data with
db_dump might help...
dumping changes, copies and nodes worked just fine. However, transactions
didn't....
$ db_dump -f representations.01 representations
db_dump: page 368987: illegal page type or format
db_dump: PANIC: Invalid argument
db_dump: DB->stat: DB_RUNRECOVERY: Fatal error, run database recovery
db_dump: close: DB_RUNRECOVERY: Fatal error, run database recovery
db_dump: dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
Anyone have any other ideas what to try ?
Best regards,
Vidar
On Thursday 17 March 2005 15:17, Vidar wrote:
> Hi
>
> I have a svn repository (0.36.0-8282) that has crashed. Doing a "svnadmin
> recover" apparently fixed the problem. However, if I then try to dump the
> repository (or do checkout, commit etc..) the repository instantly crashes
> again. So I guess someting is really messed up in the db structure and that
> "recover" is unable to fix.
>
> Since I am unable to dump the repository, I am also unable to upgrade it.
>
> So, does anyone have some input on what to try in order to get the
> repository back online again (except using a previous backup) ?
>
> Best regards,
> Vidar
--
vidar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org