SCIENTIFIC-LINUX-USERS Archives

July 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Benjamin <[log in to unmask]>
Reply To:
Doug Benjamin <[log in to unmask]>
Date:
Wed, 21 Jul 2010 11:26:30 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
Hello,

  I am writing this list to see if anyone else has come across a problem
with nfs v4 cache consistency problem.  I am running nfs v4 on SL 5.5.
The nfs v4 clients use automounted nfs partitions.

Here is the /etc/exports entry on the server:
/NFSV4exports/share/atlas 
192.168.100.2/255.255.0.0(rw,nohide,insecure,no_subtree_check,root_squash)

Here is the entry from the auto.exports file:
/export/share/atlas -fstype=nfs4 -rw,nodev,sync,netdev,nosuid 
nfsprv:/share/atlas

The problem that I am having is as follows :

When I edit a file on one nfs client,  the changes to the file are not
apparent to other clients.

When I saw the problem recently. I checked the inode, contents and
date on the file in question were different across the various client
machines.  Some machines had correct version and others had
the incorrect version.

The problem is repeatable.

Any suggestions on how to fix this problem. 

I have seen a possible solution on this tread

http://linux-nfs.org/pipermail/nfsv4/2009-January/009727.html
echo 0 >/proc/sys/fs/leases-enable (on server before mounts)

Not sure if this will create other problems.

Thank you in advance.

Regards,

Doug Benjamin

ATOM RSS1 RSS2