linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Forrest <jlforrest-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: To Automount or to Not Automount?
Date: Thu, 14 Jan 2010 12:00:48 -0800	[thread overview]
Message-ID: <hint4t$gjt$1@ger.gmane.org> (raw)

I run several Beowulf-style compute clusters
using CentOS 5. The question has come up of
whether having the compute nodes automount
needed filesystems is really necessary.
Using the automounter complicates other
aspects of configuring the cluster, but
the cluster software designers believe
that the benefits of automounting outweigh
the negatives.

In a Beowulf-style cluster there is a private
usually >= 1Gb/sec ethernet that handles the
NFS traffic. There are no routers involved.
If the network has problems that would cause
NFS to misbehave then the cluster as a whole
is probably in trouble. So, you can assume
a properly configured and functioning network.

So, I'd like to ask the NFS experts on this
list whether in a CentOS 5 environment with
NFS3 mounts over a functional private network,
would using static mounts result in any negatives
as compared to automounts. I'm especially interested
in overhead on the NFS server.

Cordially,

-- 
Jon Forrest
Research Computing Support
College of Chemistry
173 Tan Hall
University of California Berkeley
Berkeley, CA
94720-1460
510-643-1032
jlforrest-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org


             reply	other threads:[~2010-01-14 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 20:00 Jon Forrest [this message]
2010-01-14 20:58 ` To Automount or to Not Automount? Thomas Haynes
     [not found]   ` <4B4F8575.1010505-xsfywfwIY+M@public.gmane.org>
2010-01-14 21:15     ` Jon Forrest
2010-01-14 22:07       ` 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='hint4t$gjt$1@ger.gmane.org' \
    --to=jlforrest-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).