[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: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-08-24 02:03:23 CEST

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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 24 02:06:45 2005

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.