From: Brian Tinsley <btinsley@emageon.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Lorn Kay <lorn_kay@hotmail.com>,
nfs@lists.sourceforge.net, linux-ha@muc.de
Subject: Re: NFS as a Cluster File System.
Date: Thu, 09 Jan 2003 17:09:02 -0600 [thread overview]
Message-ID: <3E1E010E.4020902@emageon.com> (raw)
In-Reply-To: 20030109215019.GN2437@marowsky-bree.de
Lars Marowsky-Bree wrote:
>On 2003-01-09T19:39:50,
> Lorn Kay <lorn_kay@hotmail.com> said:
>
>>Is NFS a viable CFS? (I'm cross posting this due to a discussion on the the linux-ha list recently.)
>>
>>
>NFS might be a viable system for making content available in a cluster, given a highly available NFS sever (not that easy to do right, actually) and provided that the bandwidth and latency is good enough for you; file locking might also be a problem.
>
There are numerous threads in the NFS mailing list archives (and
probably in the NFS HOWTO - it's been quite a while since I've read it)
on how to set up a HA NFS cluster. Yes, there are quite a few pitfalls
to watch for and some applications may not behave well in this
configuration, but it's definitely achievable.
>However, it is NOT a "CFS", which people commonly use to refer to a filesystem which is distributed and usually shares the same storage system connected to all nodes.
>
Yes, good clarification.
-------------------------------------------------------
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 23:08 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
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 [this message]
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=3E1E010E.4020902@emageon.com \
--to=btinsley@emageon.com \
--cc=linux-ha@muc.de \
--cc=lmb@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox