From: Frank van Maarseveen <frankvm@xs4all.nl>
To: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Cc: Edward Hibbert <EH@dataconnection.com>
Subject: Re: [NFS] Disabling Symbolic Link Content Caching in NFS Client
Date: Tue, 3 Jun 2003 16:46:56 +0200 [thread overview]
Message-ID: <20030603144656.GA6157@iapetus.localdomain> (raw)
In-Reply-To: <CFCD2C778CF1D611B5B400065B04D5C84A736F@KENTON>
On Tue, Jun 03, 2003 at 02:33:45PM +0100, Edward Hibbert wrote:
>
> Our application consists of a number of machines collaborating on a shared
> database over NFS. We therefore require the ability to force data to be
> sync'd from the client to the backend - and at the moment we do this by
> disabling caching completely, via the noac option and acquiring and
> releasing non-exclusive locks round io calls.
>
> Any improvements in the granularity of control over NFS client-side caching
> would be very valuable to us.
To disable ac for a single directory for a certain amount of time, see
http://web.inter.nl.net/users/fvm/nfs-noac/2.4.20-noac-timeout.patch
http://web.inter.nl.net/users/fvm/nfs-noac/readme:
This patch implements /proc/sys/net/nfs/noac-timeout
When a nonzero value is written, suspend atribute caching for the current
working directory and one level of files inside for the specified number
of seconds. Attribute caching will automatically be enabled when the time
elapses. Writing a zero re-enables attribute caching as well. Reading
yields the number of remaining seconds attribute caching will be disabled.
Maybe an NFS specific ioctl would be cleaner. But the above patch can be
used even from simple scripts.
--
Frank
next prev parent reply other threads:[~2003-06-03 14:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 13:33 Edward Hibbert
2003-06-03 14:46 ` Frank van Maarseveen [this message]
2003-06-03 16:08 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 13:20 Vivek Goyal
2003-06-03 16:05 ` Trond Myklebust
2003-05-28 11:09 Vivek Goyal
2003-06-02 20:37 ` [NFS] " Ion Badulescu
2003-06-02 21:48 ` Trond Myklebust
2003-06-02 21:56 ` Trond Myklebust
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=20030603144656.GA6157@iapetus.localdomain \
--to=frankvm@xs4all.nl \
--cc=EH@dataconnection.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®