-----Original Message-----
From: Dave Camp [mailto:dave@thinbits.com]
Sent: Tuesday, August 23, 2005 8:40 PM
To: Ryan Schmidt
Cc: Sachin Patil; users@subversion.tigris.org
Subject: Re: Repeated database/logfile corruption
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
[Sachin Patil]
Thanks for the suggestions.
I moved my repositories from BDB to FSFS and all the problems have gone
away. ( atleast for now ! )
Are there any known issues in using FSFS?
-Sachin.
Received on Wed Aug 24 18:17:26 2005