All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Thomas King <kingttx@tomslinux.homelinux.org>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: Questions for article
Date: Wed, 04 Jun 2008 10:06:47 -0500	[thread overview]
Message-ID: <4846AF87.8010307@sandeen.net> (raw)
In-Reply-To: <32954.143.166.226.42.1212588962.squirrel@tomslinux.homelinux.org>

Thomas King wrote:
>> On Tue, Jun 03, 2008 at 03:48:49PM -0500, Thomas King wrote:
>>> For the most part, XFS is used for massive filesystems (hundreds of petabytes)
>> I think undreds of petabytes is not something we commonly see today :)
>> hundreds of TB is more reasonable.
> 
> If I'm going to answer his two articles, he's speaking in the context of massive
> filesystems. True, hundreds of petabytes are not common but that's the
> environment he's talking about.
> 
> From what I'm seeing from XFS, BTRFS, ext4, and HAMMER, Linux filesystems are
> going to easily keep up with the current trend. For the massive filesystems
> Henry speaks of, XFS has some new features I don't think he's aware of and needs
> to come out in this answer.
> 
> Tom King

One thing I would be careful of is not to fall into the trap of letting
Linux filesystems get bashed over things that *nobody* really has today.
 Stuff like PNFS, OSD, DIF etc are bleeding-edge for almost *everybody*

Petabyte filesystems are hard.  For *everybody*

And hundred-petabyte filesystems aren't just uncommon, they don't exist
AFAIK.

-Eric

  reply	other threads:[~2008-06-04 15:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 20:48 Questions for article Thomas King
2008-06-03 22:00 ` Martin K. Petersen
2008-06-03 22:14 ` Eric Sandeen
2008-06-03 22:19   ` Thomas King
2008-06-04  5:28   ` Christoph Hellwig
2008-06-04  5:31 ` Christoph Hellwig
2008-06-04 14:16   ` Thomas King
2008-06-04 15:06     ` Eric Sandeen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-03 15:34 Thomas King
2008-06-03 19:42 ` Justin Piszcz
2008-06-04 14:52 ` Emmanuel Florac
2008-06-02 21:50 Thomas King
2008-06-02 22:30 ` Eric Sandeen
2008-06-02 22:59 ` Andreas Dilger
2008-06-03  0:40   ` Eric Sandeen
2008-06-03 15:17     ` Thomas King
2008-06-03 15:10   ` Thomas King
2008-06-03 15:49     ` Martin K. Petersen
2008-06-03 22:07     ` Andreas Dilger

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=4846AF87.8010307@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=kingttx@tomslinux.homelinux.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.