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

Re: Berkeley DB borkage

From: Wilfredo Sánchez <wsanchez_at_wsanchez.net>
Date: 2002-11-24 18:44:30 CET

   The first time I ran svnadmin recover, it sat for a long time. I ran
top and saw that httpd was chewing up all the CPU, so I shut down
apache and shortly afterward svnadmin crashed with SIGBUS. I assumed
this is because it was "Acquiring exclusive lock on repository db" and
waiting on httpd to give up the lock. Running svnadmin repeatedly kept
crashing, still does.

   Running db_recover with no args crashes in the same manner, so it
seems the bug here isn't in svnadmin. Same with -c. Starting to look
like I'm SOL with this repository.

        -wsv

On Sunday, November 24, 2002, at 06:14 AM, Philip Martin wrote:

> Did you make sure there were no other users accessing the repository,
> did you shut down Apache? If all else fails you should be able to run
> "catastrophic" recovery (man db_recover) which will rebuild the
> database transaction-by-transaction using the log files.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 24 18:45:16 2002

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.