From: Stan Hoeppner <stan@hardwarefreak.com>
To: Lee Eric <openlinuxsource@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: 1 Gb Ethernet based HPC storage deployment plan
Date: Mon, 25 Jul 2011 08:58:21 -0500 [thread overview]
Message-ID: <4E2D767D.3020801@hardwarefreak.com> (raw)
In-Reply-To: <CAOJJ1Zod9BgFCOZkav3zYy3k2wR9ohiN0U0R0sr1QdW5CWzV6g@mail.gmail.com>
On 7/25/2011 6:52 AM, Lee Eric wrote:
> Thanks mates. So the typical storage solution for the small size
> cluster may use IP SAN as I know before. Yes, I can export the data by
> using NFS directly without iSCSI/AoE but is there any good point to
> use XFS? I just know XFS is better for parallelized read/write
> operations in local disks.
>
> By the way, is there any good advantage to use XFS as the underlying
> local filesystem for cluster/distributed/parallel filesystem?
Narrow down your candidate list of distributed filesystems and read the
documentation for each of them. I'd guess that each one of them has a
recommendation of some sort for the local storage node filesystem and
the reasoning behind the recommendation. Given the manner in which most
of them derive their parallel performance, the local filesystem is
likely not critical.
You mentioned an IP SAN. Have you looked at GFS2 and OCFS? You haven't
mentioned a workload. We could better serve you if you described the
workload.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-25 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOJJ1Zp821vD0JbGf5PuNGcW4VX4E_3SfcWYxVA4es2o0pyJXQ@mail.gmail.com>
2011-07-20 14:03 ` 1 Gb Ethernet based HPC storage deployment plan Lee Eric
2011-07-23 9:30 ` Emmanuel Florac
2011-07-24 6:30 ` Stan Hoeppner
2011-07-25 11:52 ` Lee Eric
2011-07-25 13:58 ` Stan Hoeppner [this message]
2011-07-25 14:37 ` Lee Eric
2011-07-25 21:53 ` Emmanuel Florac
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=4E2D767D.3020801@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=openlinuxsource@gmail.com \
--cc=xfs@oss.sgi.com \
/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