On Wed, 17 Jan 2007, Rainer Toebbicke wrote: > When doing an 'rm xxx', the file server does not break callbacks for > "xxx", but only for the directory containing "xxx".
Right; if the link count on the file goes to zero (the normal case), then callbacks are not broken, because since there is no new data for clients to fetch, there is no point. > Now, at least in OpenAFS 1.4.1 on Linux this does not invalidate the > cached information for "xxx" on another machine. Of course "ls xxx*" > or something will fail since the directory is correctly re-read, but > "ls -l xxx" and "cat xxx" still work if previously cached. It doesn't invalidate the cached state for vnode #nnn, but it _does_ invalidate the directory contents, and the mapping from the name "xxx" to that vnode number. I have never seen the behavior you describe, but if it exists, it is certainly a bug. _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
