Every time I try to run a svn command, it says my working copy is locked. Is my working copy corrupt?
Your working copy is not corrupt, nor is your data lost. Subversion’s working copy is journaling system, meaning that it logs everything it is about to do before it does so. If the svn client program is interrupted (Control-C, or segfault), then one or more lockfiles are left behind, along with logfiles describing unfinished business. (The`svn status’ command will show an ‘L’ next to locked directories.) Any other process that attempts to access the working copy will fail when it sees the locks. To awaken your working copy, you need to tell the svn client to finish the work.
Your working copy is not corrupt, nor is your data lost. Subversion’s working copy is a journaling system, meaning that it logs everything it is about to do before it does so. If the svn client program is interrupted violently (segfault or killed, not with Control-C), then one or more lockfiles are left behind, along with logfiles describing unfinished business. (The `svn status’ command will show an ‘L’ next to locked directories.) Any other process that attempts to access the working copy will fail when it sees the locks. To awaken your working copy, you need to tell the svn client to finish the work.
Related Questions
- How can I run DNASIS on several computers in my lab without having to move the copy protection key all the time?
- Every time I try to run a svn command, it says my working copy is locked. Is my working copy corrupt?
- I have run the perl scripts from the command line and I don see anything happening. Is it working?
