Since October, I've been doing upgrades and new installs of the OpenAFS Client
using 1.7.3200. We've recently encountered what appears to be a cache-related
bug in this version but I haven't found a way to reliably reproduce it. All
clients are running Windows 8 x64 Enterprise as the OS.
When the error occurs, it presents itself by the user seeing the following
message when trying to access any mapped AFS drives ("M" in this case):
M:\ is not accessible.
The name of the file cannot be resolved by the system.
In order to restore AFS access on the machine, I had to stop the AFS Client
service, remove the cache file, and restart the service. This is only a
temporary fix as we've had several users experience this issue multiple times.
Since this appears to be a reoccurring problem, yesterday I tried a different
approach. On a machine that was failing, I removed 1.7.3200, rebooted,
installed 1.7.3100, and rebooted again. This was done without clearing the AFS
cache and it restored AFS access.
Has anyone else encountered this problem?
--
Russ Howard
