Hi there,
with the current stable releases of svn, tortoisesvn, intellij we're
still getting the 'access denied' bug or variations of it once or
twice a week on windows XP.
http://subversion.tigris.org/issues/show_bug.cgi?id=1576
(that bug says closed, but the thread that goes along with it explains
that the patch just reduces the likelihood of being bitten)
Our incidence of this seems a bit higher than I'd expect in a stable
release, but I've noticed that we seem particularly prone to the issue
in one project, where one of the versioned directories has 500+ files
in it (oh... don't ask).
I just wanted to check if anyone knew if there is something
directory-size dependent in this bug? e.g. .svn/entries is 157k,
there's a lot of .svn-base files that would need touched in an update,
etc; I guess this might increase the window of vulnerability. Is it
worth me trying some experiments (with ludicrously large dirs) to see
if I can reproduce this more often? There seemed to be some trouble
trying to trigger it before.
Or am I on a wild goose chase for something thats resolved next release...
It would be really nice if there was a way to at least automate the
solution to this. Right now we move the broken folder out of the tree,
delete its .svn directories, update the tree to recover the missing
folder, copy the code back, and manually correct any failed 'adds'. A
better way would be to use a variation on 'svn update' that recovered
the .svn dirs without touching the working copy. 'svn repair' perhaps?
-Baz
PS we've already taken the step of excluding the folders involved from
virus scans and google desktop indexing. Its likely we have more
tag-along processes though.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 2 16:07:37 2006