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

"Attempted to lock an already-locked dir" error message

From: Anthony Kong <anthony.kong_at_ufjia.com>
Date: 2003-06-20 12:09:21 CEST

Hi, all,

I think I have stumped into another problem:

In order to test-drive it, I have created a simple repository in the local
directory. Then I would like to remove a whole dir.

I issued an command : svn delete /path/to/mydir

Then I realised that I should do it on per file basis, as I have read from
other documentation. So I ctrl-C the job.

The I issued this command: svn delete /path/to/mydir/file000

where file000 is a normal text file.

It returned OK, then I issued this command: svn commit

I found that the command did not return. I do not know if it is waiting for
comment from stdin or not. I ctrl-C it.

Then I tried this: svn commit --message "Try delete a file"

A message is returned:

svn: Attempted to lock an already-locked dir
svn: working copy locked: /tmp/test_svn/ufj
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

So i performed a cleanup as advised. And afterward I can successfully

I have a few questions:

1) which of my actions above caused the locking problem? Why is it locked
even I killed the svn command?
2) Is it now possible for the svn to delete a whole directory with all files
under it?
2) Each command took a long time to complete (around a minute, except
'delete'). Why is this? Is it because of the lock, or the operation within
the DB, or it is the expected performance?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 20 12:10:22 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.