I second the previous comments. Switch from BDB to FSFS.
Since upgrading to 1.2, Subversion crashed and locked the repository
about once a week on average while I was using BDB, and it took a
combination of Berkley's db_recover and svnadmin recover to get it
back. It was a pain especially when I was out of town or on vacation
and had to keep everybody back in the office happy.
I've had no problems since switching to FSFS a few weeks back.
On 8/23/05, Dave Camp <firstname.lastname@example.org> wrote:
> 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
> 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
> 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...
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Aug 24 04:10:33 2005