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

Re: Repository destoryed at random on OS X using new DB, etc.

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-27 17:40:52 CEST

On Tue, 2004-07-27 at 10:23, Ian Davis wrote:

> Here's the basic message I got when I tried to commit:
> [ian@cobalt ~/Sites/molprobity3]% svn ci
> svn: Commit failed (details follow):
> svn: Berkeley DB error while checkpointing after Berkeley DB
> transaction for filesystem /Users/ian/Sites/svnrepos/db:
> Invalid argument
> svn: Your commit message was left in a temporary file:
> svn: '/Users/ian/Sites/molprobity3/svn-commit.tmp'
>
>
> The same thing happens when I try updating:
> [ian@cobalt ~/Sites/molprobity3]% svn up
> svn: Berkeley DB error while checkpointing after Berkeley DB
> transaction for filesystem /Users/ian/Sites/svnrepos/db:
> Invalid argument
>
>
> After 'svnadmin recover', things get worse and this new error message persists:
> [ian@cobalt ~/Sites]% svnadmin recover svnrepos/
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
>

This looks like another case of issue 1968. Can you post a tarball of
your repository for us to inspect? Pretty please? We'd like to figure
out what's going on.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 27 17:43:44 2004

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