From: "David B. Ritch" <dritch@hpti.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Alan Robertson <alanr@unix.sh>, Lorn Kay <lorn_kay@hotmail.com>,
NFS mailing list <nfs@lists.sourceforge.net>,
linux-ha@muc.de
Subject: Re: Re: NFS as a Cluster File System.
Date: 13 Jan 2003 15:25:23 -0500 [thread overview]
Message-ID: <1042489523.2807.291.camel@localhost> (raw)
In-Reply-To: <15907.5456.68906.820989@notabene.cse.unsw.edu.au>
I agree that cache coherency is not a sensible goal for a cluster
filesystem. However, cache coherency of metadata is rather important.
For example, when one node creates a file of intermediate data, it is
important for the other nodes to be able to see that. Using actime=0 is
the conventional mechanism for allowing file creation and deletion to be
propagated quickly. Usually, one can tweak that a bit to reduce the
burden on the server. However, it might be be nice if there were a
mechanism to propagate this sort of metadata change without dumping all
metadata over a second or two old.
dbr
On Mon, 2003-01-13 at 14:36, Neil Brown wrote:
> On Thursday January 9, alanr@unix.sh wrote:
> >
> > NFS V3 and before have problems with "cache coherency". That is, the
> > different nodes in the cluster are not guaranteed to see the same contents.
> >
> > I think this is supposed to be fixed in v4.
> >
>
> NFSv4 does not try to "fix" this. It makes no attempts at "cache
> coherency" beyond what NFSv2/3 provide which is "close to open"
> cohenrence, meaning that if only one process has a file open at a
> time, then everythnig will appear coherent, and if multiple processes
> have the file open at the same time, they need to use record locking.
>
> I really don't think total cache coherency is a sensible goal for a
> network filesystem, even a cluster filesystem. It imposes lots of
> extra network traffic that most of the time will be of no value.
> If an application needs some degree of coherence, it should be
> explicit about it's needs (using open/close or locking) so that the
> protocol can provide it then, and only then.
>
> NeilBrown
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
--
David B. Ritch
High Performance Technologies, Inc.
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-13 20:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 19:39 NFS as a Cluster File System Lorn Kay
2003-01-09 21:11 ` Brian Tinsley
2003-01-09 22:04 ` Brian Jackson
2003-01-09 23:02 ` Brian Tinsley
2003-01-09 21:29 ` Alan Robertson
2003-01-13 19:36 ` Neil Brown
2003-01-13 20:25 ` David B. Ritch [this message]
2003-01-13 20:40 ` Neil Brown
2003-01-13 20:50 ` David B. Ritch
2003-01-13 22:11 ` Neil Brown
2003-01-14 15:46 ` Trond Myklebust
2003-01-14 16:01 ` Kumaran Rajaram
2003-01-14 16:08 ` Trond Myklebust
2003-01-09 21:50 ` Lars Marowsky-Bree
2003-01-09 23:09 ` Brian Tinsley
2003-01-13 4:20 ` David B. Ritch
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 22:51 Lorn Kay
2003-01-10 15:01 ` Trond Myklebust
2003-01-10 17:38 ` Greg Lindahl
2003-01-12 21:23 ` Trond Myklebust
2003-01-09 23:13 Lorn Kay
2003-01-09 23:45 ` Donavan Pantke
2003-01-10 14:51 Lever, Charles
2003-01-10 15:23 ` Brian Tinsley
2003-01-10 17:19 Lorn Kay
2003-01-12 21:29 ` Trond Myklebust
2003-01-14 16:01 Lever, Charles
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=1042489523.2807.291.camel@localhost \
--to=dritch@hpti.com \
--cc=alanr@unix.sh \
--cc=linux-ha@muc.de \
--cc=lorn_kay@hotmail.com \
--cc=neilb@cse.unsw.edu.au \
--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.