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

recovering subversion 0.35.1 repository after several stupid things happened

From: Glen <glenlist_at_model3.net>
Date: 2004-05-02 16:56:51 CEST

Hi All,
We have a 0.35.1 repository the following series of events happened and
now I can't get anything from the repository (no error messages just
long hangups).

We are using 0.35.1 on win 2003 server and Apache. Our nightly backup
was using svndump over a network share (aaagh!!! #1) (this has since
been remedied). What happened is ctrl-c was pressed on the svndmp.
After this happened noone was able to access the repository (an error
like 500 internal server error occurred). So I tried to do an "svnadmin
recover" to "unwedge" the repository. Unfortunately the machine was
rebooted during this process (aaaagh!!!! #2). When it came back up I
did another svnadmin recover and 10 hours later it finished and now when
I try to do anything with the repository (view it via a web browser or
do a checkout) nothing happens and the request just times out. For
example I have an svn checkout that has been running for 4 hours.

I have week old backups but before I resort to that I am wondering if
there is anything else I should/can do to try and recover the
repository? I won't lose anything by reverting to the backups other
than some history and the time it takes to make sure the past week of
changes get properly integrated (several hours).

Any ideas or suggestions are welcome.

I have since upgraded to 1.0.2 and changed the svndump backup to run
locally instead of via a shared network drive.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun May 2 16:57:54 2004

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.