Bug 4860 - nfs client does not changes for a long time
nfs client does not changes for a long time
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-09-02 13:02 EDT by ezharkov
Modified: 2015-09-30 21:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-16 08:05:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description ezharkov 1999-09-02 13:02:18 EDT
I am on uname -a:
Linux 2.2.12 #3 SMP Thu Sep 2 03:34:03 MDT 1999 i586 unknown
I have a number of nfs-mounted disks. The disks are on
Digital UNIX V4.0, Solaris 2.6, Linux 2.0.36.
When I edit file on any of these, the changes are not
seen by the Linux 2.2.12 for a long time (30 seconds and
more).
Comment 1 jeppesen 1999-09-04 16:25:59 EDT
I'm using RH6.0 (with the latest updates) on 3 Intel systems - one is
a NFS server. When a file is edited on one NFS client there is a
duration of up to 60 seconds before the changes can be registered on
the second NFS client.
Comment 2 Alan Cox 2000-09-16 17:32:23 EDT
Eep. Im amazed this wasnt closed and answered a very very long time ago

NFS caches data and metadata so the 30-60 seconds is actually not at all
unreasonable. The defaults are changeable via mount options
Comment 3 openshift-github-bot 2015-09-30 21:40:23 EDT
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/b6c304c7ec4514ebc5467cdbeb5934928c1d5865
Issue 4860 - missing no deployments msg when only have RCs

Note You need to log in before you can comment on or make changes to this bug.