Re: NFS Problem in Kernel 2.0.27: inode status not updated

Top Page
Delete this message
Reply to this message
Author: Warner Losh
Date:  
To: Christoph Lameter
CC: Piete Brooks, exim-users
Subject: Re: NFS Problem in Kernel 2.0.27: inode status not updated
In message <Pine.LNX.3.95.961231124010.12905B-100000@???> Christoph Lameter writes:
: POSIX NFS standards do not guarantee the accuracy of the inode
: information. Exim is definitely going beyond POSIX specs here which is
: bad and I would consider Exim buggy not Linux.

I wasn't aware that POSIX had an NFS standard. Can you give me a
reference to that body of work? POSIX generally just makes statements
about what a file system can or can't do, and what it must or must not
support. I can see them making a statement that applies to NFS such
that it doesn't have to update the caches on all machines impacted by
an invalidation operation, but I can't see them saying "NFS doesn't
need to bother with..."

Warner