linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bryan J. Smith" <b.j.smith@ieee.org>
To: Joshua Baker-LePain <jlb17@duke.edu>
Cc: 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
Subject: [Advocacy] Re: 3ware 9650 tips
Date: Mon, 16 Jul 2007 13:15:32 -0400	[thread overview]
Message-ID: <1184606132.4551.11.camel@portatux64.mobile.smithconcepts.com> (raw)
In-Reply-To: <alpine.LRH.0.999.0707161142440.25773@chaos.egr.duke.edu>

Off-topic, advocacy-level response ...  

On Mon, 2007-07-16 at 11:43 -0400, Joshua Baker-LePain wrote:
> I do so wish that RedHat shared this view...

I've been trying to convince them since Red Hat Linux 7 (and, later, 9)
that they need to realize the limits of Ext3 at the enterprise end of
the scalability spectrum -- you know, that whole market they are
seemingly saying they are the king of and a replacement for Sun?  ;->

The problem with Red Hat is that when anyone brings up an alternative to
Ext3, Red Hat falls back to arguments against other filesystems, which
is rather easy given the various compatibility issues with JFS (ported
from OS/2, requiring a lot of inode compatibility hacks -- don't get me
started with my experiences) and ReiserFS (utter lack of inode
compatibility in structures, requiring kernel-level emulation, etc...
that never seems to work, regardless of what the advocates say, let
alone the almsota always "out-of-sync" off-line repair tools).

But when you bring up XFS and its history of a stable, but advanced
inode structure, quota support from day 1, POSIX ACLs from nearly day 1,
and all the SGI team put into 2.5.3+ that is now stock kernel, they
still try to dance.  One thing I always get is "oh, its extents don't
perform well for /tmp or /var" or countless other arguments, of which I
merely respond, "all the more reason to use Ext3 for those few
filesystems, and XFS when Ext3 doesn't scale -- like for
large /home, /export, etc... filesystems."  No matter how many times I
put forth the argument that XFS complements Ext3, they seem to treat it
as yet another JFS/ReiserFS argument.

Hopeless?

-- Bryan "one of the reasons I still deploy Solaris instead of RHEL for
fileservers, even though RHL7+XFS and RHL9+XFS rocked (and are still
rocking!)" Smith


-- 
Bryan J. Smith         Professional, Technical Annoyance
mailto:b.j.smith@ieee.org   http://thebs413.blogspot.com
--------------------------------------------------------
        Fission Power:  An Inconvenient Solution


  reply	other threads:[~2007-07-16 17:15 UTC|newest]

Thread overview: 26+ 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           ` Bryan J. Smith [this message]
2007-07-16 17:40             ` [Advocacy] " Al Boldi
2007-07-16 17:48               ` Matthew Wilcox
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-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

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=1184606132.4551.11.camel@portatux64.mobile.smithconcepts.com \
    --to=b.j.smith@ieee.org \
    --cc=dgc@sgi.com \
    --cc=jlb17@duke.edu \
    --cc=jon@etelos.com \
    --cc=jpiszcz@lucidpixels.com \
    --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 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).