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

Repository Issue - Locking error on deleted files

From: Cadyn Bridgman <cbridgman_at_gmail.com>
Date: Thu, 27 Nov 2008 16:14:16 +0200

Hi,

I've got a rather perplexing problem on one our subversion repositories. The
situation is as follows:

*Configuration*
We are running VisualSVN version 1.1, which runs Subversion 1.4.6. I have
configured each repository to enforce file locking via a pre-commit hook.
If a file doesn't contain the svn-needslock attribute, the repository will
not allow the file to be committed.

*Problem*
As for the problem, I don't know exactly what happened, but the basic story
is: One of the developers removed a number of files from the repository
while having a lock on those files. If one navigates the repository using
the TortoiseSVN repositry browser, the deleted files cannot be found/seen.
The problem came in when he tried to commit a new file with the same name as
one of the ones which was deleted, and received a message which stated that
the file already exists.

*Attempts to fix it*
I have tried to delete the folder containing the problem files, but I get
the following error:

*Deleting:
D:\Work\I-Intelligence\Repo\Deloitte\CRM\branches\dev\Development
Error: Commit failed (details follow):
Error: User SVNBackups does not own lock on path
'/CRM/branches/dev/Development/Source/CRM
Service/CRMService.Model/CRMService.Model.csproj.vspscc' (currently locked
by mpalmer)
Error: If you want to break the lock, use the "Check For Modifications"
dialog.*
I cannot lock that file because I cannot get it out of the repository. If I
run an update, that file is not included in the ones retrieved from
subversion.

I have also tried running the standard repository recovery command:

*C:\Program Files (x86)\VisualSVN Server\bin>svnadmin recover
D:\Source_Control\Repositories\Deloitte
Repository lock acquired.
Please wait; recovering the repository may take some time...*
*Recovery completed.
The latest repos revision is 63.*

It runs pretty much instantly and reports no problems.

At this point, short of deleting the repository and loading everything in
again, I have no idea how to solve this issue. Can you tell me if there are
other things I can try in order to resolve this? Please let me know if
there's anything else I can tell you which might be of help.

Regards,
Cadyn Bridgman
Received on 2008-11-28 15:48:20 CET

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.