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

svn and berkeley db corruption revisited

From: Matt Otto <matt_at_klox.net>
Date: 2004-11-25 00:17:07 CET

Max Bowsher wrote:

> Yoann Vandoorselaere wrote:
>
>> On Wed, 2004-11-03 at 00:59 +0100, Yoann Vandoorselaere wrote:
>>
>>> Hi,
>>>
>>> After some try recovering a database with the help of people from #svn
>>> on Freenode, they suggested me to drop a mail here thinking you might
>>> have an insight on what to do in the current situation.
>>
>>
>> [...]
>>
>> I made a full tgz of the SVN repository available from:
>> http://prelude-ids.org/prelude-svn-repo.tgz
>>
>> I hope this will eventually help tracing the problem.
>
>
> I recovered Yoann's repository.
>
> For anyone interested, this was the "copies table type field corrupted
> from btree to recno for no apparent reason" bug.
>
> Max.

(Digging up this email from 2004-11-04.)

I've just run into the same problem Yoann had. To refresh your memory (the
email above omits the details), "svnadmin recover holter/" gives the error:

svn: Berkeley DB error while opening 'copies' table for filesystem
/var/lib/svn/holter/db:
Invalid argument
svn: bdb: call implies an access method which is inconsistent with previous
calls

I tried "db_recover -vch holter/db/" to no avail.

Max said he recovered Yoann's repository. Is there some documentation on
how to do this? Is there a way to avoid this problem in the future? I
can't find any useful information on the "copies table type field corrupted
from btree to recno for no apparent reason" bug.

System info:
Fedora Core 1
Subversion 1.1.0
db 4.1.25
apache 2.0.50

Thanks in advance,

Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 25 00:20:28 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.