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

Re: FW: FW: Berkeley DB error while opening `changes' table for filesystem [#8143]

From: Jamin W. Collins <jcollins_at_asgardsrealm.net>
Date: 2003-05-26 21:51:04 CEST

On Mon, May 26, 2003 at 04:34:46PM +0200, Sander Striker wrote:
> [Forwarded to the dev@ list with permission]
> Sander
> -----Original Message-----
> From: Keith Bostic [mailto:bostic@abyssinian.sleepycat.com]
> Sent: Saturday, May 24, 2003 4:45 PM
> To: striker@apache.org
> Cc: support@sleepycat.com
> Subject: Re: FW: Berkeley DB error while opening `changes' table for
> filesystem [#8143]
> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=38046
> > We seem to see a lot of these with db 4.1.25. Whether it is our
> > usage pattern or a plain 'ol bug in db 4.1.25 (the 4.0 series doesn't
> > show this at all) I don't know.
> How easy is it to reproduce this problem?

I've only had it happen the one time. From the discussion on IRC and
reading the list archives, it appears that the exact cause is still

> If you run recovery on this same repository again, does it fail in the
> same way each time?

Subversion's recover fails every time with the error referenced in the
list archive link. Berkeley db_recover appears to complete (both normal
and catastrophic). However, the db itself remains unusable. db_verify
on the other hand does indicate a problem.

> If running recovery on this same repository reproduces the error, and
> the databases and log files aren't too large, can you please compress
> and archive them, and upload them to:
> ftp.sleepycat.com/incoming

The archive has been uploaded, it's called coding-horked-20030523.tar.gz

Jamin W. Collins
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 26 21:51:59 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.