Wilfredo Sánchez <wsanchez@wsanchez.net> writes:
> 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.
Wait, how exactly are you running db_recover?
db_recover -ve -h repository/db/ ?
db_recover -c -h repository/db/ ?
I just want to make sure you're not making the classic mistake of
pointing db_recover at the repository's root directory, rather than
the repository's db subdir.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 24 19:00:21 2002