Linux NFS development
 help / color / mirror / Atom feed
From: "Stefan Bauer" <sb@plzk.de>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: exporting single directory to many hosts - locking and concurrent writes a problem?
Date: Tue, 28 Jul 2015 13:17:18 +0200	[thread overview]
Message-ID: <zarafa.55b764be.798b.51558f0c6ce3c9b0@srv1.localhost> (raw)

Hi,

I'm evaluating filesystems for concurrent access(rw) from different hosts and came across cluster file systems like GFS2 and OCFS2.
Is NFS in a way also able to deal with concurrent reads / writes ?

I have two hosts that need to share a single storage. Access to this storage can be concurrent and to the same files at the same time.

What are the limitations / advantages on NFS compared to cluster file systems?

NFS looks like a simple solution for this to me. Cluster file systems require locking and fencing with addiontional components. I want to keep it as simple as possible.

I would be happy to get your ideas and thoughts on this.

Thank you.

Kind regards,

Stefan

                 reply	other threads:[~2015-07-28 11:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=zarafa.55b764be.798b.51558f0c6ce3c9b0@srv1.localhost \
    --to=sb@plzk.de \
    --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