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

Re: svn vicious circles: can't set file..... read-write:Access is denied/or/working copy locked -> cleanup failed

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Fri, 10 Oct 2008 14:11:45 +0400

2008/10/10 Pompi Diplan <podiplan_at_microsoft.com>:
> Obviously, any ***other*** ideas are welcome J.

If the working copy is screwed beyond any repair, the best
choice is to check out a new working copy, or at least
the subtree of that fails.

Such things do really happen sometimes. The cleanup command
cannot fix any possible error.

It can fix aborted commit or update operations, and clean the
lock that remains on your WC during those operations, but it cannot
fix any arbitrary errors, especially those where some control
information is lost.

Actually, it is very easy to screw up the working copy, if you are
inaccurate: any arbitrary modification of those files inside .svn
subdirectory, and you are screwed. Luckily, it only affects that
one level (and folders below it), and you can re-checkout only
that subtree.

Possible causes:
1. Manual removal or loss of .svn subdirectory.

2. Moving folders around without issuing respective svn wc
management commands, see
http://tortoisesvn.net/most-forgotten-feature

3. It can be that your IDE moves or copies files around (deletes
.svn subfolder, or copies it from other directory), e.g. during the
build process. If that is the case, you should not store that directory
in subversion, but should add it to svn:ignore property of its parent.

4. Intervening, preventing subversion access to its files while it
performs its operations. It can be caused by some antivirus
software or by the filesystem (e.g. when using SAMBA shares).
Upgrade and proper configuration may be required (contact the
vendor).

5. It is possible, though unlikely, that Subversion screws its
own directories during some operation. Most common operations
and a lot more are automatically tested before making a release,
and if you did not do anything unusual, you must be safe.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-10 12:11:56 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.