From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Phil Oester" <phil@theoesters.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: NFS caching issues on 2.4
Date: 07 Jun 2001 00:55:58 +0200 [thread overview]
Message-ID: <shs3d9dtdz5.fsf@charged.uio.no> (raw)
In-Reply-To: <LAEOJKHJGOLOPJFMBEFEEEFNDNAA.phil@theoesters.com>
In-Reply-To: "Phil Oester"'s message of "Wed, 6 Jun 2001 13:48:48 -0700"
>>>>> " " == Phil Oester <phil@theoesters.com> writes:
> I've stumbled upon a wierd NFS caching issue on 2.4 which does
> not seem to exist in 2.2. Our www docroot is NFS mounted on a
> NetApp 760. We have a cron job which make changes to the
> index.html every 5 minutes.
> Recently, we upgraded all the web servers to 2.4 and noticed
> that there were big delays in seeing these 5 minute updates.
> Yet, an ls -l in the nfs directory on each of the servers
> clearly shows the new timestamp. However, a cat of the file
> shows that it is the old version (sometimes up to 1 hour old).
> I was using NFSv3, so decided to try NFSv2, but got the same
> results.
> I reverted to 2.2.19 on the boxes (which are RedHat 7.1
> incidentally), and these problems went away.
> Any ideas why this is happening?
The main suspect would be if you're mmapping the file while the cron
job updates your file on the server. This would means that the cache
invalidation breaks (see all the conditions in
invalidate_inode_pages()).
Cheers,
Trond
prev parent reply other threads:[~2001-06-06 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 20:48 NFS caching issues on 2.4 Phil Oester
2001-06-06 22:55 ` Trond Myklebust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shs3d9dtdz5.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@theoesters.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox