On Sunday 17 October 2004 16:51, Jay Cornwall wrote:
> Eric Gillespie wrote:
> >>I have a Subversion repository set up that seems to become
> >>corrupt with alarming regularity.
> >
> > That's life with the berkeley back-end. I recommend switching to
> > fsfs.
This is FUD. I admit that FSFS is a bit easier to cope with, but BDB is
just fine when the multiple access methods are set up correctly.
> Thanks, I hadn't taken the time to read up on FSFS before. Seems fairly
> straightforward so I've dumped a backup of my repository into an FSFS
> repository; let's hope it performs a little better!
>
> >>db_recover: PANIC: fatal region error detected; run recovery"
> >
> > I love it when recover tells you to run recovery. When that
> > happens, i restored from backups. Before switching to fsfs, we
> > had a recoverable wedge about once a month, and one of these
> > non-recoverable wedges about once every other month. If
> > catastrophic recovery fails, i don't know that there is another
> > way to recover. I just restored from backups at that point.
>
> I've had to restore from backups many times over the last few months.
> Thankfully it's just an experimental repository; goodness only knows
> how much work I might have lost had I been using it for a live project.
What version of BDB are you using? 4.1.x is known to have a shared memory
bug, that Subversion brings out in full color, especially on machines
with multiple processors. You should be using the latest stable version,
4.2.52.
With that said, I have Subversion setup for about 14 developers and have
used it for over 2 years with the BDB backend. Not once have I run into
any problems like this.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 17 23:09:14 2004