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

Top Page
Delete this message
Reply to this message
Author: Christoph Lameter
Date:  
To: Philip Hazel
CC: exim-users
Subject: Re: NFS Problem in Kernel 2.0.27: inode status not updated
On Tue, 31 Dec 1996, Philip Hazel wrote:

ph10 >I will add this note to Exim's README file.
ph10 >
ph10 >>        noac           Disable  all  forms  of  attribute  caching
ph10 >>                       entirely.  This extracts a  server  perfor
ph10 >>                       mance  penalty  but it allows two different
ph10 >>                       NFS clients to get reasonable good  results
ph10 >>                       when  both  clients are actively writing to
ph10 >>                       common filesystem on the server.
ph10 >> 
ph10 >> This would also solve the problem but gives a performance hit.


Please do not add this. Instead include the patch and mention the version
number of the kernel fixing this problem as soon as it is released.


ph10 >But surely a mail spool is precisely the case of two different NFS
ph10 >clients (the MTA and the MUA) "actively writing to a common filesystem
ph10 >on the server"?

Yes. But we want speed. I think we rather change the NFS code than
using the noac option. That is the difference to commercial OS. You
can simply change things if necessary.

--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5