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

Re: Repository died after a "successful" add and commit

From: Nicolas Goutte <nicolasg_at_snafu.de>
Date: 2005-06-13 12:08:43 CEST

On Friday 10 June 2005 23:35, Brian C. Van Essen wrote:
> Hello, I was trying to get my advisor to use our subversion
> repository today and during what seemed a normal sequence of
> operations, the repository has corrupted itself and we are being
> forced to pull a backup. I am trying to figure out what went wrong,
> so here is the sequence of events.
>
> Background:
> Two of us use the repository mainly via ssh remote access, and have
> had no problems.
>
> Today's sequence of events:
> Today, I had our advisor checkout the repository via a "file://" URL
> from a nfs mounted drive.

Have you read the FAQ and the handbook? As far as I have understood, it is
written there that you cannot use Berkeley DB on NFS, not even on a NFS
system claiming to support Berkeley. (And from the logs below, you *are*
using Berkeley, not FSFS!)

(...)
> Recovery completed.
> svn: Berkeley DB error while opening environment for filesystem /
> projects/lis/rapid/svnrep/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: PANIC: fatal region error detected; run recovery
> tebo:~/tmp_sb/svnrep vanessen$ svnadmin verify /projects/lis/rapid/
> svnrep
> svn: Berkeley DB error while opening environment for filesystem /
> projects/lis/rapid/svnrep/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: PANIC: fatal region error detected; run recovery
(...)

Have a nice day!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 13 12:16:15 2005

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