At 9:45 AM -0600 5/23/03, D.J. Heap wrote:
>Jack Repenning wrote:
>>I think you can get "access denied" if someone else is dorking with
>>_the_directory_ that contains the file.
>
>Hmm, do you mean like adding/removing files in the same dir or
>moving/deleting the directory?
Well, I'm not exactly sure *what* I mean; it's a hazy memory. As
best I recall, it went like this:
We had a distributed service that involved files (something called
"ClearCase"; perhaps you've heard of it?). We had some files stored
on a Windows (VOB) server (WinNT 4.0sp6, I'm pretty sure). We had
both Windows and Unix clients of these files (don't ask, I just don't
want to go there). We had a Windows NFS-server product installed to
make that happen. Occasionally, things would lock up. Eventually
(with the help of the NFS product vendor) we discovered that the NFS
server would "lock" the directories in some sense, and at times
neglect to lift the lock. We were never, so far as I can recall,
clear even on what user operation led to the problem, let alone what
code the server was executing (and failing to un-execute). We had a
tool from the NFS vendor that would relinquish these locks, which we
ended up running every five minutes or something like that. But I
might be wrong about nearly any detail in that list.
But I do recall that the precise symptom depended on the interface
you used to test it. The most reliable test was to open a cmd.exe
window, on the server, and "dir" around until you found a directory
with owner shown as "Unavailable". Other symptoms included several
different errors, including (I think) "Access Denied" and "Illegal
Access."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 23 19:21:10 2003