lkml.org 
[lkml]   [1996]   [Dec]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: NFS Problem in Kernel 2.0.27: inode status not updated
Date
In article <Pine.LNX.3.95.961228101457.19421A-100000@waterf.org>,
Christoph Lameter <clameter@waterf.org> wrote:
>
>There is a new mailer available for Linux called exim. It sports some
>locking scheme that claims to work better under NFS. But it does not
>work under Linux.
>
>It first opens a lockfile with a unique name and then links that one
>to the classic /var/spool/mail/username.lock lockfile. Then it checks the
>number of links on that file. If there are two then the lock is
>successful. Problem is Linux fstat call always returns 1 for the number of
>links even though a link() was done immediately prior.
>
>I wonder if some kind of caching in the NFS client part of the kernel
>does not properly update the inode information in this situation?

Did you mount the fs with the "noac" (no attribute caching) option?

Mike.
--
| Miquel van Smoorenburg | "Sticky tape is like the Force - it has a |
| miquels@drinkel.cistron.nl | dark side, it has a light side, and it |
| ----8<--------------8<---- | holds the universe together" - Carl Zwanig |

\
 
 \ /
  Last update: 2005-03-22 13:38    [W:0.031 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site