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: Mon, 17 Jul 2006 14:49:18 -0400	[thread overview]
Message-ID: <1153162159.13961.3.camel@localhost> (raw)
In-Reply-To: <m1hd1gksev.fsf@minerva.ceride.gov.ar>

On Mon, 2006-07-17 at 15:17 -0300, Mario Storti wrote:
> Hi all, 
> 
> We have still problems with NFS in our Beowulf cluster. The original
> post is here
> 
> http://thread.gmane.org/gmane.linux.nfs/9564/focus=9566
> 
> The news are that we reproduced the problem on Scientific Linux 4.2
> and also without VNFS. In addition we have taken a tethereal capture
> that may help in understanding the problem. 
> 
> In brief we have a Beowulf class cluster built on Scientific Linux
> (Beryllium) 4.2, (kernel 2.6.9-22.0.1). The cluster is disk-less
> (nodes don't have hard disks) based on the Warewulf package. NFS
> traffic is reduced by using VNFS filesystems at the nodes. However we
> reproduced the problem in a configuration with disks at the nodes. 
> 
> The problem is that for some files in user accounts if we make some
> modifications to the file in the server, this changes are not seen in
> the compute nodes. The NFS server is NFS3 and with the standard
> configuration (8 instances of the server and default parameters). The
> cluster has 20 nodes at this time, but we have made experiments with a
> `cloned' cluster and even with only two nodes the problem persist.
> 
> The experiment is as follows: We change a text file in a user account
> with Emacs and checking whether the change is seen in the compute
> nodes. Sometimes the change is immediately seen in the compute nodes,
> but many times some nodes don't see the change. 
> 

This is a FAQ that has been well-publicised and discussed to death on
this list:
  http://nfs.sourceforge.net/#faq_a8

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-17 18: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 [this message]
2006-07-18 11:19   ` Mario Storti
2006-07-18 13:48     ` Trond Myklebust
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=1153162159.13961.3.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