On Mon, 14 Apr 2008, Rainer Toebbicke wrote:
We ran into this over a year ago and fixed it, but I must have forgotten to
submit the fix.
It is actually the detection of a "cell" in the mount point string which
triggers the (loosely consistent) fakestat handling - it's treated like a
foreign
We ran into this over a year ago and fixed it, but I must have
forgotten to submit the fix.
It is actually the detection of a "cell" in the mount point string
which triggers the (loosely consistent) fakestat handling - it's
treated like a foreign cell and the mount point is never "completely
If a client runs with the -fakestat[-all] option, and has a file cached
that resides in the root directory of a volume affected by fakestat, it
fails to invalidate its cache for this file when it's deleted:
ClientA: touch x
ClientB: ls -l x
... 0 Apr 10 13:10 x
ClientA: echo a >> x
ClientB: ls
