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

Re: svn server crashes, corrupt repository

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-09-04 16:06:40 CEST

Vidar <vl-list@ez.no> writes:

> However, We have now been running 0.28.2 for 1 day and now it has crashed
> again.
> I get:
> $ svnlook youngest nextgen
> svn: Berkeley DB error
> svn: Berkeley DB error while checkpointing after Berkeley DB transaction for
> filesystem nextgen/db:
> DB_INCOMPLETE: Cache flush was unable to complete
> Do I have to run "svnadmin recover" ?

This error means you've run out of lockfiles, I think. (Is that
correct, Sander?) That's strange, because this error is exactly the
bug that 0.28.2 is supposed to fix (compared to 0.28.0 and 0.28.1.)
Are you *sure* that your mod_dav_svn module is 0.28.2?

I think you need to run recovery, yes.

> Ealier when we got stall lock (in older versions) on the repository, I have
> just done a "shortcut" and delete the __db.00* files. Is this safe ?

Unless you understand BerkeleyDB *very* well, this sounds like risky
behavior to me. I wouldn't do that.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 4 16:08:46 2003

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.