All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: attack upon XFS, misinformation abounds, linux-raid list
Date: Mon, 10 Jun 2013 15:02:16 -0500	[thread overview]
Message-ID: <20130610200216.GQ20932@sgi.com> (raw)
In-Reply-To: <51B45CFD.20500@hardwarefreak.com>

Hey Stan,

On Sun, Jun 09, 2013 at 05:46:21AM -0500, Stan Hoeppner wrote:
> In a recent linux-raid list thread here:
> http://marc.info/?l=linux-raid&m=137072140106867&w=2
> 
> seriously flawed arguments against the reliability of XFS, and even the
> performance of XFS, are made.  The OP even quotes Dave's LCA
> presentation as a performance reason to avoid XFS.  The party really
> gets started at paragraph 7.
> 
> I made a brief effort to debunk his claims and explained that he can't
> have O_PONIES, that he should use fsync or O_DIRECT, etc for data
> safety.  To non experts/advanced filesystem users, his long winded
> argument may be persuasive.  Obviously none of you experts has time to
> debunk every such post, but this one may be worth a read at least,
> especially given the weight Google gives to vger lists.

I gave it a quick read, but since I'm not on linux-raid I don't have a good way
to reply to Steve.  Could you bounce that message over?  I'd be happy to try to
address a point or two...

Thanks,
	Ben

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

  parent reply	other threads:[~2013-06-10 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 10:46 attack upon XFS, misinformation abounds, linux-raid list Stan Hoeppner
2013-06-09 12:13 ` Ric Wheeler
2013-06-10  9:43 ` Stefan Ring
2013-06-10 13:44   ` Eric Sandeen
2013-06-10 20:02 ` Ben Myers [this message]
2013-06-11  7:12 ` Steve Bergman
2013-06-12  1:12   ` Stan Hoeppner

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=20130610200216.GQ20932@sgi.com \
    --to=bpm@sgi.com \
    --cc=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 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.