Jamie Jackson wrote:
> I'm getting wedged working copies.
>
> I'm not completely sure whether it's isolated to windows working
> copies that are accessed by a windows share or not, but I think that's
> the main problem scenario. However, I have advised developers not to
> access the WC in this manner, but am still having this sort of
> problem. Instead of having developers access the remote working copies
> via network share, I have a scheduled job that runs on the remote
> servers (which host the working copies), which issues a cleanup, then
> an update, every 3 minutes.
>
> After a while, the updater scheduled job fails, because the the WC is wedged.
Well, that's the wrong solution. If somebody is doing a Subversion command in
there that locks the wc, then this will break the internal wc locks.
> Once the working copy gets wedged, I RDP into the machine and attempt
> a local cleanup, which gives me messages like:
>
> "can't open directory [blah\blah\blah\].svn\tmp"
> "the system cannot find the path specified"
>
> The only way I've found to fix these sorts of problems is to remove
> the offending parent directories (from the file system) until I can
> get a successful cleanup, then I update to get the files back.
>
> Can anyone shed any light?
Well, you need to figure out why they are getting wedged in the first place. Is
wedged just meaning there's a lock in it?
If you have multiple svn clients trying to work in the same working copy, that
can do it.
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 1 18:13:06 2007