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

Re: Repeated database/logfile corruption

From: Dave Camp <dave_at_thinbits.com>
Date: 2005-08-24 02:39:46 CEST

On Aug 23, 2005, at 5:03 PM, Ryan Schmidt wrote:

> On 23.08.2005, at 23:10, Sachin Patil wrote:
>> Ever since I started access using ssh, my repository seems to get
>> corrupted.
>>
>> Error Berkeley DB error while checkpointing after Berkeley DB
>> transaction of
>> filesystem /svnrepo/myproj/db:
>> Error Invalid argument
>> Error bdb: DB_ENV->log_flush:LSN of 51/193480 past current end-of-
>> log of
>> 1/10488
>> Error bdb: Database environment corrupt; the wrong log files may
>> have been
>> removed or incompatible database files imported from another
>> environment.
>>
>
> I cannot tell you why this is happening, but I can recommend that
> you put the latest Subversion on your server (currently 1.2.1; soon
> 1.2.3) and convert your repository from BDB to FSFS. In 6 months on
> this list, I have seen a fairly constant stream of posts about
> problems with BDB repository wedging, and very few problems with
> FSFS repositories. This is not because of inherent problems with
> BDB, but rather because of inherent problems with the way in which
> Subversion uses BDB. Since the Subversion and BDB teams have yet to
> completely resolve these issues, I suspect converting will help you.

Yes, get off BDB as fast as possible. General consensus among users
on the list is that it will eventually get corrupted. In every case
moving to FSFS has apparently made all the problems go away. It has
for me...

Dave
Received on Wed Aug 24 02:40:53 2005

This is an archived mail posted to the Subversion Users mailing list.