From: Ming Zhang <mingz@ele.uri.edu>
To: Nathan Scott <nathans@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: stable xfs
Date: Tue, 18 Jul 2006 21:15:53 -0400 [thread overview]
Message-ID: <1153271753.2669.276.camel@localhost.localdomain> (raw)
In-Reply-To: <20060719095400.A1936041@wobbly.melbourne.sgi.com>
thanks a lot for this detail explanation!
i will check both 2.6.17 -stable release and sles kernel. unfortunately,
i only play with RHEL so far.
Ming
On Wed, 2006-07-19 at 09:54 +1000, Nathan Scott wrote:
> On Mon, Jul 17, 2006 at 11:30:23AM -0400, Ming Zhang wrote:
> > Hi All
> >
> > We want to use XFS in all of our production servers but feel a little
> > scary about the corruption problems seen in this list. I wonder which
> > 2.6.16+ kernel we can use in order to get a stable XFS? Thanks!
>
> Use the latest 2.6.17 -stable release, or a vendor kernel (SLES is
> particularly good with XFS, as SGI works closely with SUSE).
>
> The current batch of corruption reports is due to one unfortunate
> bug that has slipped through our QA testing net, which happily is
> a fairly rare occurence (it was a very subtle bug).
>
> XFS also tends to get a bad rap (IMO) from the way it reports on-disk
> corruption and I/O errors in critical data structures, which is quite
> different to many other filesystems - it dumps a stack trace into the
> system log (alot of people mistake that for a panic) and "shuts down"
> the filesystem, with subsequent accesses returning errors until the
> problem is resolved.
>
> > ps, one friend mentioned that XFS has some issue with LVM+MD under it.
> > Is this true?
>
> No.
>
> cheers.
>
next prev parent reply other threads:[~2006-07-19 2:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 15:30 stable xfs Ming Zhang
2006-07-17 16:20 ` Peter Grandi
2006-07-18 22:36 ` Ming Zhang
2006-07-18 23:14 ` Peter Grandi
2006-07-19 1:20 ` Ming Zhang
2006-07-19 5:56 ` Chris Wedgwood
2006-07-19 10:53 ` Peter Grandi
2006-07-19 14:45 ` Ming Zhang
2006-07-22 17:13 ` Peter Grandi
2006-07-20 6:12 ` Chris Wedgwood
2006-07-22 17:31 ` Peter Grandi
2006-07-19 14:10 ` Ming Zhang
2006-07-19 10:24 ` Peter Grandi
2006-07-19 13:11 ` Ming Zhang
2006-07-20 6:15 ` Chris Wedgwood
2006-07-20 14:08 ` Ming Zhang
2006-07-20 16:17 ` Chris Wedgwood
2006-07-20 16:38 ` Ming Zhang
2006-07-20 19:04 ` Chris Wedgwood
2006-07-21 0:19 ` Ming Zhang
2006-07-21 3:26 ` Chris Wedgwood
2006-07-21 13:10 ` Ming Zhang
2006-07-21 16:07 ` Chris Wedgwood
2006-07-21 17:00 ` Ming Zhang
2006-07-21 18:07 ` Chris Wedgwood
2006-07-24 1:14 ` Ming Zhang
2006-07-22 18:09 ` Peter Grandi
2006-07-22 17:47 ` Peter Grandi
2006-07-22 15:37 ` Peter Grandi
2006-07-18 23:54 ` Nathan Scott
2006-07-19 1:15 ` Ming Zhang [this message]
2006-07-19 7:40 ` Martin Steigerwald
2006-07-19 14:11 ` Ming Zhang
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=1153271753.2669.276.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=nathans@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 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.