public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Giuseppe Ghibò" <ghibo@mandriva.com>
To: b.j.smith@ieee.org
Cc: Simon Matter <simon.matter@invoca.ch>,
	xfs-bounce@oss.sgi.com, Stuart Levy <slevy@ncsa.uiuc.edu>,
	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, xfs@oss.sgi.com
Subject: Re: [Advocacy] Re: 3ware 9650 tips
Date: Tue, 17 Jul 2007 22:20:54 +0200	[thread overview]
Message-ID: <469D24A6.6080409@mandriva.com> (raw)
In-Reply-To: <582908739-1184695294-cardhu_decombobulator_blackberry.rim.net-122921225-@bxe015.bisx.prod.on.blackberry>

Bryan J Smith wrote:

> Matter, Simon wrote:  
>> I know that XFS had and maybe still has some minor issues -
>> but, if RedHat decided to use XFS and put the same effort into it
>> like they did with Ext3, those problems would have gone long ago.
> 
> Ditto.  XFS was the ultimate, complementary filesystem to Ext3.
> 
> In all honesty, I'm just looking forward to ZFS on RHEL, sorry to say.

ZFS won't appear officially in Linux until there will be change of
license, so right now it's released in userspace.

> Although I don't see that being "proven" for years, so I'm with XFS "on my own"
> when I deploy RHEL - which is, many times, the only viable filesystem.
> 
> --  

Indeed XFS is a lot faster than ext3 on many task (e.g. copy/moving
or delete huge files o creating filesystems or dumping with xfsdump),
and worked fine, until linux kernels around 2.6.15|16|17|18 when it had serious problems about
data corruptions. Furthermore when you run xfs_repair to fix such errors, you find that it lost
all the directory names, and places restored files into "random" dirs
named with "number" names.

See for instance:

http://lkml.org/lkml/2006/8/4/97
http://lkml.org/lkml/2006/8/28/88
or http://qa.mandriva.com/show_bug.cgi?id=24716

and sound the fix is not easy to be backportable to kernel series older than 2.6.18,
such as 2.6.17 (used for instance in ubuntu 7.04 and mandriva 2007.1).

Also in the recent 2.6.20|21 kernel series I found it has serious problems of
performance, especially when used in softraid (e.g. for storing
the vmware huge filedisks images a simple "sync" takes fifteen minutes in a raid1).

Bye
Giuseppe.

       reply	other threads:[~2007-07-17 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <582908739-1184695294-cardhu_decombobulator_blackberry.rim.net-122921225-@bxe015.bisx.prod.on.blackberry>
2007-07-17 20:20 ` Giuseppe Ghibò [this message]
2007-07-18  1:41   ` [Advocacy] Re: 3ware 9650 tips David Chinner
2007-07-18  8:47     ` Giuseppe Ghibò
     [not found] <alpine.LRH.0.999.0707131356520.25773@chaos.egr.duke.edu>
     [not found] ` <Pine.LNX.4.64.0707131434470.31742@p34.internal.lan>
     [not found]   ` <4697CA4D.6020304@etelos.com>
2007-07-13 19:36     ` Justin Piszcz
2007-07-16  2:41       ` David Chinner
2007-07-16 15:43         ` Joshua Baker-LePain
2007-07-16 17:15           ` [Advocacy] " Bryan J. Smith
     [not found]             ` <200707162040.00062.a1426z@gawab.com>
2007-07-16 17:48               ` Matthew Wilcox
2007-07-16 18:38                 ` 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

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=469D24A6.6080409@mandriva.com \
    --to=ghibo@mandriva.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-ide-arrays@lists.math.uh.edu \
    --cc=simon.matter@invoca.ch \
    --cc=slevy@ncsa.uiuc.edu \
    --cc=xfs-bounce@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox