public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Best filesystems ?
Date: Sat, 23 Oct 2010 16:28:56 -0500	[thread overview]
Message-ID: <4CC35398.6000308@hardwarefreak.com> (raw)
In-Reply-To: <19651.9652.631329.903552@tree.ty.sabi.co.uk>

Peter Grandi put forth on 10/23/2010 1:13 PM:

> * XFS is like JFS, and with somewhat higher scalability both as to
>   sizes and as to higher internal parallelism in the of multiple
>   processes accessing the same file, and has a couple of nice
>   features (mostly barrier support, but also small blocks and large
>   inodes). Its major limitation are internal complexity and should
>   only be used on 64b systems. It can support single filesystems
>   larger than 10-15TB, but that's stretching things.

I'm surprised you mentioned Lustre and not CXFS, especially given the
mailing list you posted this diatribe to.  Beasts of a different breed,
but both cluster oriented.  And, apparently you're not familiar with
NASA Advanced Supercomputing (NAS) Division at Ames Research Center.
They've got some multi hundred terabyte filesystems to show you:

http://www.nas.nasa.gov/Resources/Systems/archive_storage.html

> * Lustre works well as a network parallel large file streaming
>   filesystem. It is however somewhat unstable and great care has to
>   be taken in integration testing because of that.

Integration testing?  I guess you mean the linkers and compilers on the
build machines?  The Lustre client library gets linked directly into
every application that runs on the compute nodes--it's entirely user
space code.  Or at least this is the way it used to be IIRC.  To do any
general work with the files (move/copy/etc) you had to log onto an
object storage server node.  Maybe this has changed with newer revs.

> I currently think that JFS, XFS and Lustre cover more or less all
> common workloads. 

I'll agree with the first two, but Lustre isn't used for "common"
workloads.  See above.

> I occasionally use 'ext2' or NTFS for data
> exchange between Linux and MS-Windows.

Most people use Samba, C/DVD-Rs, or thumb drives for this purpose.  If
you have _that_ much data to move between systems, Samba over GigE
yields similar throughput to mounting a USB or eSATA disk, without the
hassle.  If Samba throws up a wall and you can't tune settings around
it, use rsync or something similar.  Dragging HDs between systems is
so... 80s. ;)

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-10-23 21:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 23:04 avoid mbox file fragmentation Stan Hoeppner
2010-10-19 23:42 ` Dave Chinner
2010-10-20  2:36   ` Stan Hoeppner
2010-10-20 11:31     ` Peter Grandi
2010-10-20  3:03   ` Stan Hoeppner
2010-10-21  1:55     ` Dave Chinner
2010-10-20 11:50   ` Peter Grandi
2010-10-21  2:00     ` Dave Chinner
2010-10-21 16:39       ` Peter Grandi
2010-10-21 20:06         ` Best filesystems ? Andrew Daviel
2010-10-22  2:47           ` Stan Hoeppner
2010-10-23 18:13           ` Peter Grandi
2010-10-23 20:16             ` Emmanuel Florac
2010-10-26  0:55               ` hank peng
2010-10-26  7:19                 ` Emmanuel Florac
2010-10-23 21:28             ` Stan Hoeppner [this message]
2010-10-24  0:17             ` Steve Costaras
2010-10-24 18:27             ` Michael Monnerie
2010-10-24 20:52               ` Emmanuel Florac
2010-10-20 11:21 ` avoid mbox file fragmentation Peter Grandi

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=4CC35398.6000308@hardwarefreak.com \
    --to=stan@hardwarefreak.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