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

RE: Berkeley repository broken

From: Krijn Schaap <krijn_at_stoneroos.nl>
Date: Tue, 23 Sep 2008 17:06:53 +0200

Ryan,

According to that, I'm using version 4.4. I've been able to restore my
repository from a backup, and only lost the two revisions committed
yesterday, so the damage is limited. Additionally I switched the repository
to fsfs, hopefully that prevents these issues in the future.

Regards,
Krijn Schaap

-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2008c_at_ryandesign.com]
Sent: dinsdag 23 september 2008 17:03
To: Krijn Schaap
Cc: users_at_subversion.tigris.org
Subject: Re: Berkeley repository broken

On Sep 23, 2008, at 3:13 AM, Krijn Schaap wrote:

> As of this morning, my subversion repository is broken. I tried to
> recover it using svnadmin recover, but I get the following error:
>
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> svnadmin: Berkeley DB error for filesystem 'db' while opening 'nodes'
> table:
> Invalid argument
> svnadmin: bdb: file nodes (meta pgno = 0) has LSN [1083][429767].
> svnadmin: bdb: end of log is [1083][354707]
> svnadmin: bdb: db/nodes: unexpected file type or format
>
> I'm using svnadmin, version 1.4.2 (r22196)
> compiled Nov 10 2006, 17:39:50
>
> Any thoughts?

What version of BDB do you have? Did you recently upgrade?

You can find out what version of BDB your repository thinks it should be
using by looking here:

http://subversion.tigris.org/faq.html#divining-bdb-version

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-23 18:28:52 CEST

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.