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

RE: Unchanged Working Copy Reports Lock

From: Grady, Shane <shane.grady_at_fmr.com>
Date: Wed, 28 May 2008 15:28:26 -0400

Updating with some possibly relevant info and still hoping for a

CruiseControl v2.6 is running in multi (2) threaded mode.

Might the root cause of the issue I'm seeing be a result of concurrently
executing SVN updates from the same windows client (even though they're
targeted at different local workspaces)?

Would it increase the relevancy to know the updates are from the same

Thanks in advance,

-----Original Message-----
From: Grady, Shane
Sent: Wednesday, May 21, 2008 11:54 AM
To: users_at_subversion.tigris.org
Subject: Unchanged Working Copy Reports Lock


I have a reoccurring issue where a local working copy that has not been
modified is reporting a lock, on what appear to be random locations
(directories only?); ideas or suggestions would be appreciated.

I have a continuous integration build environment (Ant and CruiseControl
driven) setup where one of the first steps is to update the local
working copy; it then actually copies the checkout to a separate
location where the build will be preformed. The Ant code is nothing

  <taskdef name="svn" classname="org.tigris.subversion.svnant.SvnTask"
    <update dir="${sccs.dir}"/>
    <status path="${sccs.dir}" revisionProperty="repository.revision"/>
  <copy todir="${build.home}">
    <fileset dir="${sccs.dir}" includes="**/*"/>

I've had this setup for quite some time with numerous projects all
utilizing the same build files and RARELY would run into a situation
where the working copy became locked or corrupted and would need to
either manually "cleanup" or even a corrupted disk repaired (though that
would typically occur in the build copy vs. the SVN local working copy).

I recently added a couple projects that are much more active and
building quite frequently (10-20 times daily) and have been doing so for
a few weeks; however, a couple days ago the builds began failing due to
the SVN update having failed due to locked directories...I don't believe
a locked file has been encountered yet.

No modifications occur in the local working copy so I'm curious how /
where this lock is coming from? An update to the HEAD revision of the
same directory from a different working copy executes/updates without

Output from the working copy in question:

s\dojo\dojo>svn update
svn: Working copy 'rpc' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for

s\dojo\dojo>svn status .
  L rpc

s\dojo\dojo>svn info
Path: .
Repository Root: http://dfpcmsbos02:7804/svn/TAAC
Repository UUID: 349b959b-e90c-0410-8cfa-f701a4186ad7
Revision: 12178
Node Kind: directory
Schedule: normal
Last Changed Author: a438523
Last Changed Rev: 9956
Last Changed Date: 2008-04-10 09:55:10 -0400 (Thu, 10 Apr 2008)

A "svn diff" shows no change, confirmed by the absence of a "M" in the
output of "svn status" above.

Environment Info:
Client Info:
Win Server 2003 SP2
SVN Client version 1.4.3
Server Info:
Solaris 8
SVN Server version 1.4.3

Is this due to the frequency or volume of updates to the same working
copy? Any ideas and/or suggestions appreciated!


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-28 21:28:47 CEST

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.