From: Alan Robertson <alanr@unix.sh>
To: Lorn Kay <lorn_kay@hotmail.com>
Cc: nfs@lists.sourceforge.net, linux-ha@muc.de
Subject: Re: NFS as a Cluster File System.
Date: Thu, 09 Jan 2003 14:29:58 -0700 [thread overview]
Message-ID: <3E1DE9D6.7040406@unix.sh> (raw)
In-Reply-To: F112Sbh29cM3oryKFRJ0001248d@hotmail.com
Lorn Kay wrote:
>
> Is NFS a viable CFS? (I'm cross posting this due to a discussion on the
> the linux-ha list recently.)
>
> NFS has a bad reputation probably due to (at least) the following:
>
> It has been used in networking environments where different server
> hardware configurations (NICS, drivers, etc.) running different
> operating systems have connected to each other (in many-to-many
> configurations).
>
> It “grew up” on networks that were perhaps unstable, or immature
> (“Someone’s kicked the token ring coax cable laying on the floor again”)
> long before switches were common place, and the network was loaded down
> with all kinds of network traffic.
>
> It wasn’t understood very well. Since the default mount options
> worked, system administrators often didn’t fully understand the
> ramifications of their NFS client mount option choices.
>
> It relied on UDP, which is susceptible to huge retransmission
> efforts on noisy or lossy networks.
>
> NFS was used over many-hop WAN connections.
>
> NFS servers were often used for many other tasks, not just NFS.
>
>
> A cluster configuration, however, offers several advantages over the
> typical NFS configuration:
>
> All NFS clients (the cluster nodes) run the same operating system
> (Linux).
>
> All clients run the same version of NFS and the kernel.
>
> All clients use the same network tuned configuration.
>
> A physical network can be dedicated to NFS. (Using a high quality
> switch, with short data-center-only cable runs.)
>
> All clients connect to one NFS server.
>
> The NFS server is a high-quality dedicated machine (Net App, EMC, etc.)
>
> Only one mount point need be used with one set of mount options.
>
> Linux clients can use TCP instead of UDP.
>
> Except for the vagaries of the load placed on the cluster nodes, this
> sounds like a test lab environment. If NFS can’t work in this
> environment where will it ever work?
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.
--
Alan Robertson <alanr@unix.sh>
"Openness is the foundation and preservative of friendship.... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-09 21:30 UTC|newest]
Thread overview: 18+ 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 [this message]
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
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 23:13 Lorn Kay
2003-01-10 3:34 ` Alan Cox
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=3E1DE9D6.7040406@unix.sh \
--to=alanr@unix.sh \
--cc=linux-ha@muc.de \
--cc=lorn_kay@hotmail.com \
--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.