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

Re: Corrupted repository report

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2004-06-17 21:38:36 CEST

On Thu, Jun 17, 2004 at 01:19:11PM -0400, Scott Lawrence wrote:
> On Thu, 2004-06-17 at 12:31, Ben Collins-Sussman wrote:
> > On Thu, 2004-06-17 at 11:20, Scott Lawrence wrote:
> >
> > > Transmitting file data .........................svn: Commit failed (details follow):
> > > svn:
> > > Berkeley DB error while committing Berkeley DB transaction for filesystem /scm/rep/sipXtackLib/db:
> > > Invalid argument
> >
> > This looks like a BDB 4.1 bug we've seen before, whereby a table's type
> > gets mysteriously changed. Is that what you're using? If so, we
> > recommend rebuilding apache's apr-util to use BDB 4.2 ASAP.
>
> I don't think so: rpm -qa | grep db4
> db4-4.2.52-3
>
> there is a db4-4.1.25-8 further down in the list, but I'm pretty sure
> that svn is not using that (because the rpm wouldn't install until I had
> the 4.2 version in place).

Using David's RPMs for systems based on DB 4.1.25, you end up with both
DB 4.1.25 and 4.2.52 linked into httpd processes, both using the same
symbols. It is totally unsurprising that this combination ends up with
random database corruption.

joe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 17 21:39:53 2004

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.