From: "J. Bruce Fields" <bfields@fieldses.org>
To: Yudong Gao <stgyd@umich.edu>
Cc: Benny Halevy <bhalevy@panasas.com>, linux-nfs@vger.kernel.org
Subject: Re: Supported cluster file system in v4.1
Date: Wed, 23 Jun 2010 14:46:20 -0400 [thread overview]
Message-ID: <20100623184620.GD28346@fieldses.org> (raw)
In-Reply-To: <AANLkTimvyf-KbN-XWkawxp3SHG_WgHJ_sBXnlJjWMIjM@mail.gmail.com>
On Wed, Jun 23, 2010 at 10:14:09AM -0700, Yudong Gao wrote:
> Hi Benny,
>
> Thanks a lot for the reply! I will check exofs.
>
> We are looking for a block-based cluster file system that can be
> deployed on top of a cluster of commodity machines and can use the
> machines' local storage instead of using a SAN. We find that OCFS2 is
> a good candidate.
As far as I can tell OCFS2 and GFS2 are identical in their requirement
for a shared disk.
--b.
> Is it possible to use OCFS2 as the storage server in
> pNFS?
prev parent reply other threads:[~2010-06-23 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 17:17 Supported cluster file system in v4.1 Yudong Gao
2010-06-23 6:49 ` Benny Halevy
2010-06-23 17:14 ` Yudong Gao
2010-06-23 17:33 ` Andy Adamson
2010-06-23 18:46 ` J. Bruce Fields [this message]
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=20100623184620.GD28346@fieldses.org \
--to=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stgyd@umich.edu \
/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