Bug: Lock on a file that is no longer existing.
From: Wilbert Jansen <wjansen_at_cordys.com>
Date: Thu, 9 Jul 2009 10:52:04 +0200
I tried to find this bug in the open issues on Subversion bugs, but wasn't able to find it which surprises me since I've seen it twice in the last week. I ignored the first time, since that was on a repos that I was simply testing/hacking on and without much thought removed it and created a new one.
The below describes how we got there as good as possible. Note: this is NOT a valid reproduction schema, as in it does not result in the bug. Unfortunately the second repos that had the error has been deleted at this time as well.
- Created the SVN repos with Visual SVN Server 1.6.4
- A file in the repos mhf_core.jar got renamed to mhf.jar and was moved to another folder (the who/how is unfortunately obscure). That worked, as in that the mhf.jar is present in the repos and gives no issues.
- Tried to delete the folder that contained the original mhf_core.jar directly from Visual SVN manager. This gives an error that I don't have a lock on mhf_core.jar (since it was created by another user. When logged in with the other user's id and tried deleting, gives an error empty token).
- Tried deleting by checking out the contents on file system. The mhf_core.jar was not present in that folder.
- Tried deleting by Tortoise version 1.6 .3 and then do a commit. This does not work, it gives an error that mhf_core.jar file is locked: 'Cannot verify lock on path '/trunk/somefolderstructure/jarfile.jar'; no username available'
- The file does however no longer exist in repository. It does not get checked out and it is not there according to the repo browser.
- The only way we found to remove this lock and delete the folder was by deleting the entire repository.
Hopefully this gives an idea. I've tried to reproduce this a few times, but wasn't able to. Not sure what is missing.
This is an archived mail posted to the Subversion Dev mailing list.