All of lore.kernel.org
 help / color / mirror / Atom feed
From: ralph gonzalez <rgonzale@ibl.bm>
To: nfs@lists.sourceforge.net
Cc: ralph gonzalez <rgonzale@ibl.bm>
Subject: Force client page cache invalidation?
Date: Tue, 24 Feb 2004 14:30:26 -0400	[thread overview]
Message-ID: <403B9842.9070001@ibl.bm> (raw)

We tend to run multiple applications on a single client, which all
mmap (usually readonly) the same file on an nfs-mounted volume.
If the file changes on the server, then we would like clients to
see these changes upon closing/reopening this file.

On Solaris (which we are moving from), this would work fine. However
Linux 2.4.22-10mdk (nfs utils 1.0.5) seems to be unwilling to reload
the file cache *when another application already has the file mmapped*.

Therefore each time the file is editted on the server, we have to
force all applications mapping this file (on the client in question)
to close the file *simultaneously*, and then allow them to reopen the
mapping.

*Question*: Instead, is there a way to force the client to reload
the file cache (exclusively for this file)? (So when we subsequently
close/open the file in each application asynchronously, they see the
correct pages.) Maybe there's a simple option or utility I'm missing?

A separate problem is that the file attributes are cached, so the
file cache is only reloaded if we force the client to reread the
file attributes whenever the file is editted on the server. This we
accomplish by the trick of locking/unlocking the file immediately
after opening it, to avoid disabling mount-level attribute caching
via the noac option.

Thanks for any suggestions!
-- 
Ralph Gonzalez
rgonzale@ibl.bm



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2004-02-24 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 18:30 ralph gonzalez [this message]
2004-02-24 20:06 ` Force client page cache invalidation? trond.myklebust
2004-02-26  8:57   ` Olaf Kirch
2004-02-26 12:35     ` trond.myklebust
  -- strict thread matches above, loose matches on Subject: below --
2004-02-25 14:05 ralph gonzalez

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=403B9842.9070001@ibl.bm \
    --to=rgonzale@ibl.bm \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.