Hello, Has anyone had cache inconsistency problems with Windows clients?
Two Windows 7 64-bit OpenAFS 1.7.3 clients are not seeing the same files when they look at the same volume via two different RW mount points. One client is making changes, and the other client is just reading the files, but both are accessing the volume via an RW mount point so that a 'vos release' won't be necessary. We've seen this problem occasionally before with earlier versions of OpenAFS too, but never bothered much because it seemed to fix itself eventually. But now, the only thing that makes the files show up is a reboot. An "AFS -> flush volume" command from the context menu does not solve the problem. Some additional info: the server housing this volume is CentOS 6 64-bit, OpenAFS 1.4.14. We see messages like these scattered about in the FileLog for the client that is not seeing the changed files: FindClient: stillborn client 74024d60(d16fe8cc); conn 180213d0 (host MY.CLI.ENT.IP:7001) had client f402fa30(d16fe8cc) CB: RCallBackConnectBack (host.c) failed for host MY.CLI.ENT.IP:7001 CB: WhoAreYou failed for host 34015890 (MY.CLI.ENT.IP:7001), error 1 Could these messages be indicating a problem? (They appear frequently in the logs and I cannot tell if they correspond to specific read or write actions on the clients.) -- Jonathan.Nilsson at uci dot edu Social Sciences Computing Services SSPB 1265 | 949.824.1536
