On Tue, 10 Jan 2012 09:56:40 -0800 Russ Allbery <[email protected]> wrote:
> This generally means that you're losing callbacks, which leads me to > immediately bs suspicious of firewalls or NAT. Since AFS is > UDP-based, the client can think that it has a "connection" with the > server for the callback channel, but either the NAT mapping or the > firewall rule may have timed out. Then the server can't send callback > breaks to the client to tell them that something has changed in a > directory, but the client is none the wiser. If this is the problem, you should see messages in FileLog mentioning that it can't break callbacks, or it can't contact client X, etc, while mentioning the IP address of clients experiencing issues. -- Andrew Deason [email protected] _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
