You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Glen <gl...@model3.net> on 2004/05/02 14:56:51 UTC

recovering subversion 0.35.1 repository after several stupid things happened

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.

regards,
Glen




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: recovering subversion 0.35.1 repository after several stupid things happened

Posted by Glen <gl...@model3.net>.
I can do a svnadmin recover but it takes about 12 hours to process.  I 
know it is a long running process but that seems very long the 
repository size is 360 megs.

I deleted db.lock then copied it from another working repository and 
tried to do an svn checkout file::///repos/ and it appears to be hanging 
still (1 hour with no messages).



Ben Collins-Sussman wrote:

>On Sun, 2004-05-02 at 09:56, Glen wrote:
>  
>
>>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.
>>    
>>
>
>Are you still able to 'svnadmin recover'?
>
>As an experiment, try removing and then recreating repos/locks/db.lock.
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>  
>

Re: recovering subversion 0.35.1 repository after several stupid things happened

Posted by Ben Collins-Sussman <su...@collab.net>.
On Sun, 2004-05-02 at 09:56, Glen wrote:
> 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.

Are you still able to 'svnadmin recover'?

As an experiment, try removing and then recreating repos/locks/db.lock.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org