How to fix Subversion lock error

Question

How do you fix the Subversion/Subclipse error "Attempted to lock an already-locked dir"?

Googling shows people routinely encounter this error, and the only solution I've seen posted is to run Subclipse's Team->Cleanup command. Unfortunately, I get this error when I run the Team->Cleanup command. Are there any other options?

score 122 · Answer 1 · answered Feb 15 '14 at 01:49

122

I had similar problem. Team->Refresh/Cleanup Solved my problem

answered Feb 15 '14 at 01:49

user3312309

1,229
1
8
2

3

sometimes the Cleanup will not solve the problem, try to delete the lock file in .svn hidden folder – Re MiDa Mar 21 '15 at 10:50

score 29 · Answer 2 · answered Jan 12 '17 at 18:40

29

I tried all suggestion from this thread but the only one that worked is:

go to the folder on which the project locked folder is stored
execute svn cleanup

answered Jan 12 '17 at 18:40

Andrea Girardi

4,337
13
69
98

2

This worked for me, I think subversion couldn't make cleanup if directory locked from any terminal. thanks – AsyncTask Nov 15 '17 at 13:52
4

Worked for mee too, unlike the GUI manipulations in Eclipse. This should be the accepted answer. – GreenhouseVeg Feb 01 '18 at 10:49
1

Worked for me too. Unlike any menu option in Eclipse – Julian Wright Aug 10 '18 at 05:35
1

This Worked for me. Team -> Refresh/Clean Up was not working for me. – Beeti Sushruth Nov 11 '19 at 05:49

Vijay Bhatt · Answer 3 · 2015-07-22T05:56:30.867

28

Error : Attempted to lock an already-locked dir svn: Working copy 'C:\work\myproject\workspaces\HPDP' locked.

Solution: Worked for me.

        Right-click on project-->Team-->Refresh/Cleanup

edited Jul 22 '15 at 05:56

answered Feb 19 '15 at 05:57

Vijay Bhatt

1,351
13
13

This has saved me twice now. – Jack BeNimble May 12 '16 at 17:04

score 14 · Answer 4 · edited May 23 '17 at 12:10

14

I get this too. I go to the directory (not in Eclipse) where the files are, go into the .svn dir and delete the file called lock.

Flip back to Eclipse and continue.

There is a similar question here Problems committing file to SVN repository

edited May 23 '17 at 12:10

Community

1
1

answered Mar 07 '13 at 02:12

robot-nofollow

177
1
4

score 12 · Answer 5 · edited Oct 19 '17 at 13:53

12

I solved this problem by doing these:

Right click on your project.
Click on Team
Click Refresh/Cleaup

edited Oct 19 '17 at 13:53

Gajotres

57,309
16
102
130

answered Feb 17 '17 at 12:40

Mhandroid

219
3
13

score 8 · Answer 6 · answered Aug 15 '19 at 06:24

8

Just Right Click on Project

Click on Team
Click Refresh/Cleaup

this will remove all the current lock files created by SVN

hope this will help !!!!

answered Aug 15 '19 at 06:24

Akitha_MJ

3,882
25
20

score 6 · Answer 7 · answered Jan 26 '17 at 11:10

6

After the same problem with "phantom lock" the only solution was:

1) Disconnect the Project Eclipse->Team->Disconnect (select option to delete .svn folder)

2) Than "reconnect" Eclipse->Team->SVN->Share Project. Ignore the warning about better do an checkout. After this all worked fine.

Cleanup and Restart was no solutions, also Scan Locks did not show anything.

answered Jan 26 '17 at 11:10

SkateScout

815
14
24

1

This works and can solve the problem within Eclipse. – user2652379 Jul 18 '18 at 04:03

score 5 · Answer 8 · edited Mar 11 '19 at 07:21

5

We had the same repeating problem. It's a disaster. What can you do if cleanup and unlock does not help because there is no existing lock?

Search the hidden .svn folder in your directory structure. It contains a wc.db file which is an sql lite file.
Open it with an sql client, e.g. DBeaver. Add an sql lite connection to the dbeaver by selecting the wc.db file.
Open the WC_LOCK table. You can see one or more rows that contains the URL which was mentioned in the phantom lock error window.
Delete these rows from the table.
Try to update your project from the repo.
If you use more than 1 repo in 1 project (externals) another phantom lock may appear during the update. In this case repeat the process with that folder.

edited Mar 11 '19 at 07:21

gudok

4,029
2
20
30

answered Mar 11 '19 at 00:18

Szabó Ákos

51
1
3

1

Please consider editing your question to add some indentation making your steps into a proper list. – JJJ Mar 11 '19 at 00:59
This is a genius solution...! Thanks a lot, it worked like a charm. – tarekahf Mar 03 '20 at 07:25
Thanks! In most cases the UI based solution is enough. But not always. This is the case when you need to go deeper. – Szabó Ákos Dec 14 '20 at 19:35

score 4 · Answer 9 · answered Apr 28 '16 at 18:20

4

Old question, but none of the above solutions worked for me. What did work was to close eclipse, then using Tortoise, right click on the project in Windows Explorer and choose 'TortoiseSVN' -> 'Clean up', then just use the default checkboxed items (Clean up working copy status, include externals), then hit OK.

This cleaned up the folder, then I was able to update and commit files as normal.

answered Apr 28 '16 at 18:20

Justin

2,559
3
27
33

This worked for us. Great answer. This occurs when you commit too many individual files within a small frame of time. – Mindsect Team Feb 28 '17 at 21:55

score 4 · Answer 10 · answered Jul 11 '16 at 04:24

4

Using SVN 1.8, deleting lock file does not help (lock file does not exists).

Refresh/Cleanup did not solve either.

What did solve:

1) Backup your directory, just incase...
2) Team... Disconnect. Choose to remove .svn files
3) Add it again to SVN.

Note: In my case, error was due to loss of network connection during initial commit.

answered Jul 11 '16 at 04:24

Cedric Simon

4,571
4
40
52

3

More recently, just performing "snv cleanup /path/to/my/project" from the command line saved me – Cedric Simon Apr 03 '17 at 15:43

score 2 · Answer 11 · answered Dec 16 '15 at 06:57

2

I have faced same problem. I solved this by Right click on project --->Team----> Refresh/cleanup

answered Dec 16 '15 at 06:57

score 2 · Answer 12 · answered Mar 18 '12 at 06:27

2

svn help unlock

And find locker after all - lock isn't needed in most cases

answered Mar 18 '12 at 06:27

Lazy Badger

94,711
9
78
110

score 1 · Answer 13 · answered Mar 19 '19 at 12:24

We don't have an external SVN server. I was working on a PC with Windows 7 Enterprise, and I was using Eclipse subversion plugin as an SVN client. The problem in my case occurred when the commit of a file took to much time due to network problem that forced me to restart my PC.

After the restart I started getting this error: XXX file already locked.

The solution was to install (TortoiseSVN), right click on the SVN project folder --> TortoiseSVN --> cleanup.

I hope that this post would be a help to someone.

score 1 · Answer 14 · answered Apr 09 '20 at 11:55

1

use tortoise svn to cleanup with 'break write locks' option checked

answered Apr 09 '20 at 11:55

Shilpa R

11
1

score 0 · Accepted Answer · answered Nov 06 '13 at 14:55

I tried recursively deleting all lock files, but that just resulted the error "Path is not a working copy". I ended up having to do Team->Disconnect and then Team->Share. Upon reconnect, it complained about existing .svn files, which it deleted. Now it seems to be working.

score 0 · Answer 16 · answered Apr 17 '14 at 09:51

0

I spent hours looking for a solution to the "Attempted to lock an already-locked dir" error I was receiving in IBM RAD. Finally, I guessed to type:

unlock <directory path>

in the RAD console and... volia I could finally syncronize my files!!

answered Apr 17 '14 at 09:51

samwhocan

29
2
7

score 0 · Answer 17 · answered Apr 22 '19 at 08:09

0

Go to the metadata directory as below

your workspace>projectname>.metadata

inside this metada directory, there will be a lock file. Delete this lock file.

Restart eclipse and rebuild project. It worked for me !

answered Apr 22 '19 at 08:09

coding_with_sabs

121
1
2
10

score 0 · Answer 18 · answered Jun 07 '19 at 06:47

0

Subversion supports a command named "Cleanup"; it is used to release the locks on a project

answered Jun 07 '19 at 06:47

Brajesh

1,515
13
18

score 0 · Answer 19 · answered Jan 14 '20 at 08:45

I solved a similar problem. SVN client gave me an error:

"svn: E200002: Failed to create new lock."

I tried everything including "Cleanup" and "Still Lock" but with no success. Then I solved the problem simply, I went to my svn server and deleted the locks folder:

at "c:/svn/my_repository/locks"

It turned out that there are broken files in it.

score 0 · Answer 20 · answered Aug 04 '20 at 12:20

0

Refresh/Cleanup did not work for me. What worked:

1) File -> Switch workspace - choose a different workspace
2) afterwards switch back to the original workspace

answered Aug 04 '20 at 12:20

Raluca Preisler

1
1

How to fix Subversion lock error

20 Answers20