Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Mario Storti <mstorti@intec.unl.edu.ar>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS synchronization problems on Beowulf cluster
Date: Tue, 18 Jul 2006 09:48:51 -0400	[thread overview]
Message-ID: <1153230531.22180.7.camel@localhost> (raw)
In-Reply-To: <m1ejwjtb2t.fsf@minerva.ceride.gov.ar>

On Tue, 2006-07-18 at 08:19 -0300, Mario Storti wrote:
> > This is a FAQ that has been well-publicised and discussed to death on
> > this list:
> >   http://nfs.sourceforge.net/#faq_a8
> 
> I tried to mount with `nocto' and `noac' options without success. Also
> tried acregmax=0,acdirmax=0. We are trying to determine if there is
> some mistake in our configuration or if this is a `normal'
> behavior. Your post seems to suggest that this is a `normal' behavior.
> However, previously we had a cluster with RedHat 7.1 (kernel
> 2.2.16-22, NFS version 2) and we didn't had problems like this.  We
> tried to use NFS version 2 on the new cluster and the problem
> persists. So I think that this is problem with the configuration and we
> are still trying to solve the problem tuning the mount/server options.

Please reread the article. This is _normal_ behaviour. NFS has never
been guaranteed to be cache coherent in this way.

NFS checks its data cache on calls to open()/opendir(), and on taking a
lock. That is all.

Cheers,
  Trond


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2006-07-18 13:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 18:17 NFS synchronization problems on Beowulf cluster Mario Storti
2006-07-17 18:49 ` Trond Myklebust
2006-07-18 11:19   ` Mario Storti
2006-07-18 13:48     ` Trond Myklebust [this message]
2006-07-20 10:49       ` Mario Storti
2006-07-20 11:04         ` Trond Myklebust
2006-07-20 11:35           ` Mario Storti
  -- strict thread matches above, loose matches on Subject: below --
2006-05-31 19:23 Mario Storti
2006-06-01 13:58 ` Mario Storti
2006-06-01 14:25   ` Peter Staubach
2006-06-01 14:54     ` Mario Storti
2006-06-01 15:56       ` Peter Staubach
2006-06-01 16:35         ` Mario Storti
2006-06-01 17:22           ` Peter Staubach
2006-06-01 18:50             ` Mario Storti

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=1153230531.22180.7.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=mstorti@intec.unl.edu.ar \
    --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