All of lore.kernel.org
 help / color / mirror / Atom feed
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:50:56 -0500	[thread overview]
Message-ID: <1042491056.2806.312.camel@localhost> (raw)
In-Reply-To: <15907.9286.737016.365337@notabene.cse.unsw.edu.au>

That makes sense.  However, it is common practice in many shops to write
intermediate data files with some sort of serial number or timestamp in
the name, and for the next step in the process to look for data using
"ls" with a wildcard.  When doing that, you don't know what the name of
the next file might be, so you can't simply open it.

While I agree that this is not the most ideal method for coordinating
processing, it is widely used and I have found a need to support it.

We've also had processes fail with a "file not found" error when trying
to read a file recently written by a process on another node.  It has
always been my belief that this was a failure when a process tried to
open the file, and the local metadata cache had not yet been updated. 
Just to clarify - are you saying that the open system call should have
contacted the server, even if the local cached information said that the
file (and perhaps its parent directory) did not exist?

Thanks,

dbr

On Mon, 2003-01-13 at 15:40, Neil Brown wrote:
> On  January 13, dritch@hpti.com wrote:
> > 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.
> 
> If the 'other nodes' open the file and look in it, then they should
> see current data (if they don't it's a bug).  If they just 'stat' it
> to see if it has changed then they may see and old timestamp.
> 
> I recommend openning the file.  It is an explicit way for the
> application to say "I really want to know the current state of this
> file". 
> 
> NeilBrown
-- 
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

  reply	other threads:[~2003-01-13 20:51 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
2003-01-13 20:40       ` Neil Brown
2003-01-13 20:50         ` David B. Ritch [this message]
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=1042491056.2806.312.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.