linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Steve Bergman <sbergman27@gmail.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Is this expected RAID10 performance?
Date: Sun, 09 Jun 2013 08:09:44 -0400	[thread overview]
Message-ID: <51B47088.4000501@redhat.com> (raw)
In-Reply-To: <CAO9HMNHVNQcU=FumFnLRd9b0msMr8fr0z6SmL82dksu+6CNXYA@mail.gmail.com>

On 06/08/2013 03:56 PM, Steve Bergman wrote:
> Simply Googling "xfs zero" and sorting by date yields pages and pages
> of recent report hits.

This is a just silly. Try googling for "Santa Claus lives at the North Pole" or 
"Do pixies really exist". Both queries will give you rock solid evidence that 
you can share will us, down to a specific mail address for Santa :)

For that matter, try googling "ext4 zero length files".

In my experience, which is based on first hand experience and direct knowledge, 
what enterprise users and enterprise storage array vendors actually use when 
constructing Linux based storage devices, XFS is by far the more popular choice.

To be clear, you absolutely can lose data with *any* file system if you 
misconfigure your storage, ignore the barriers, etc. That definitely includes ext4.

The way ext4 and xfs both do things is a lot closer these days (mainly because 
the ext4 developers have continually harvested good ideas from XFS with XFS 
occasionally doing the same from ext4).

For any application, I always encourage users to try out a few file systems and 
see what is best for them.

It is a lot more interesting to share your actual setup and results. Much less 
interesting to echo uninformed, old claims.

Regards,

Ric




  parent reply	other threads:[~2013-06-09 12:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 19:56 Is this expected RAID10 performance? Steve Bergman
2013-06-09  3:08 ` Stan Hoeppner
2013-06-09 12:09 ` Ric Wheeler [this message]
2013-06-09 20:06   ` Steve Bergman
2013-06-09 21:40     ` Ric Wheeler
2013-06-09 23:08       ` Steve Bergman
2013-06-10  8:35         ` Stan Hoeppner
2013-06-10  0:11       ` Joe Landman
2013-06-09 22:05     ` Eric Sandeen
2013-06-09 23:34       ` Steve Bergman
2013-06-10  0:02         ` Eric Sandeen
2013-06-10  2:37           ` Steve Bergman
2013-06-10 10:00             ` Stan Hoeppner
2013-06-10  7:19           ` David Brown
2013-06-10  0:05     ` Joe Landman
  -- strict thread matches above, loose matches on Subject: below --
2013-06-09 23:53 Steve Bergman
2013-06-10  9:23 ` Stan Hoeppner
2013-06-06 23:52 Steve Bergman
2013-06-07  3:25 ` Stan Hoeppner
2013-06-07  7:51 ` Roger Heflin
2013-06-07  8:07   ` Alexander Zvyagin
2013-06-07 10:44     ` Steve Bergman
2013-06-07 10:52       ` Roman Mamedov
2013-06-07 11:25         ` Steve Bergman
2013-06-07 13:18           ` Stan Hoeppner
2013-06-07 13:54             ` Steve Bergman
2013-06-07 21:43               ` Bill Davidsen
2013-06-07 23:33               ` Stan Hoeppner
2013-06-07 12:39       ` Stan Hoeppner
2013-06-07 12:59         ` Steve Bergman
2013-06-07 20:51           ` Stan Hoeppner
2013-06-08 18:23 ` keld

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=51B47088.4000501@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=sbergman27@gmail.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;
as well as URLs for NNTP newsgroup(s).