From: Matthew Wilcox <matthew@wil.cx>
To: Al Boldi <a1426z@gawab.com>
Cc: "Bryan J. Smith" <b.j.smith@ieee.org>,
Joshua Baker-LePain <jlb17@duke.edu>, David Chinner <dgc@sgi.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Jon Collette <jon@etelos.com>,
linux-ide-arrays@lists.math.uh.edu, linux-raid@vger.kernel.org,
xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: [Advocacy] Re: 3ware 9650 tips
Date: Mon, 16 Jul 2007 11:48:01 -0600 [thread overview]
Message-ID: <20070716174801.GM13826@parisc-linux.org> (raw)
In-Reply-To: <200707162040.00062.a1426z@gawab.com>
On Mon, Jul 16, 2007 at 08:40:00PM +0300, Al Boldi wrote:
> XFS surely rocks, but it's missing one critical component: data=ordered
> And that's one component that's just too critical to overlook for an
> enterprise environment that is built on data-integrity over performance.
>
> So that's the secret why people still use ext3, and XFS' reliance on external
> hardware to ensure integrity is really misplaced.
>
> Now, maybe when we get the data=ordered onto the VFS level, then maybe XFS
> may become viable for the enterprise, and ext3 may cease to be KING.
Wow, thanks for bringing an advocacy thread onto linux-fsdevel. Just what
we wanted. Do you have any insight into how to "get the data=ordered
onto the VFS level"? Because to me, that sounds like pure nonsense.
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-07-16 17:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.0.999.0707131356520.25773@chaos.egr.duke.edu>
2007-07-13 18:35 ` 3ware 9650 tips Justin Piszcz
2007-07-13 18:54 ` Jon Collette
2007-07-13 19:36 ` Justin Piszcz
2007-07-16 2:41 ` David Chinner
2007-07-16 12:22 ` David Chinner
2007-07-16 12:39 ` Bernd Schubert
2007-07-16 15:50 ` Eric Sandeen
2007-07-16 22:21 ` David Chinner
2007-07-16 15:43 ` Joshua Baker-LePain
2007-07-16 17:15 ` [Advocacy] " Bryan J. Smith
2007-07-16 17:40 ` Al Boldi
2007-07-16 17:48 ` Matthew Wilcox [this message]
2007-07-16 18:28 ` [RFC] VFS: data=ordered (was: [Advocacy] Re: 3ware 9650 tips) Al Boldi
2007-07-16 19:02 ` Matthew Wilcox
2007-07-16 18:38 ` [Advocacy] Re: 3ware 9650 tips Bryan J. Smith
2007-07-16 17:34 ` Stuart Levy
2007-07-16 18:44 ` [Advocacy] " Bryan J. Smith
2007-07-17 17:30 ` Simon Matter
2007-07-13 19:04 ` Joshua Baker-LePain
2007-07-13 23:30 ` Michael Tokarev
2007-07-14 1:23 ` Andrew Klaassen
2007-07-14 8:08 ` Justin Piszcz
2007-07-14 16:10 ` Andrew Klaassen
2007-07-14 16:11 ` Justin Piszcz
2007-07-14 16:14 ` Andrew Klaassen
2007-07-14 16:18 ` Justin Piszcz
2007-07-14 9:04 ` Mikael Abrahamsson
2007-07-14 16:11 ` Andrew Klaassen
[not found] <582908739-1184695294-cardhu_decombobulator_blackberry.rim.net-122921225-@bxe015.bisx.prod.on.blackberry>
2007-07-17 20:20 ` [Advocacy] " Giuseppe Ghibò
2007-07-18 1:41 ` David Chinner
2007-07-18 8:47 ` Giuseppe Ghibò
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=20070716174801.GM13826@parisc-linux.org \
--to=matthew@wil.cx \
--cc=a1426z@gawab.com \
--cc=b.j.smith@ieee.org \
--cc=dgc@sgi.com \
--cc=jlb17@duke.edu \
--cc=jon@etelos.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide-arrays@lists.math.uh.edu \
--cc=linux-raid@vger.kernel.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.