We have discovered another instance in which a Windows client might be unable to access volume data. If the volume was cached by the client and then moved, salvaged or otherwise taken offline, the Windows client would never move the volume from the "offline" state to the "not busy" state. In this case, being "offline" is distinct from all of the known servers being "down". In the "down" case, the Windows client has a background thread to periodically test the reachability of the server. In this case, there was no code in place to attempt to find a new source for the volume data.
A correction for this problem has been developed and was committed to the OpenAFS repository. The fix will be available in the final 1.4.0 release.
Post a Comment