From: Dave Chinner <david@fromorbit.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: XFS status update for August 2010
Date: Mon, 6 Sep 2010 09:36:35 +1000 [thread overview]
Message-ID: <20100905233635.GW7362@dastard> (raw)
In-Reply-To: <20100905185600.GD27623@1wt.eu>
On Sun, Sep 05, 2010 at 08:56:00PM +0200, Willy Tarreau wrote:
> On Sun, Sep 05, 2010 at 11:08:09PM +1000, Dave Chinner wrote:
> > That being said, I've been running
> > my laptop and my production machines (except for the backup target)
> > for a couple of months now with it and haven't had any problems...
>
> Fine, this is typically the type of info I need. Thus I'll be using
> it with an eye on any potential FS-related problem.
Thanks.
> Are there any plans to use that option by default once it gets enough
> testing ? I'm asking because I had to convert from XFS to reseirfs at
> least twice due to slow metadata, but I tend to trust XFS a lot more
> (especially due to dirty failures I experienced a few years ago with
> reiserfs - corrupted file tails upon power cut).
>From Documentation/filesystems/xfs-delayed-logging-design.txt:
2.6.37 Remove experimental tag from mount option
=> should be roughly 6 months after initial merge
=> enough time to:
=> gain confidence and fix problems reported by early
adopters (a.k.a. guinea pigs)
=> address worst performance regressions and undesired
behaviours
=> start tuning/optimising code for parallelism
=> start tuning/optimising algorithms consuming
excessive CPU time
2.6.39 Switch default mount option to use delayed logging
=> should be roughly 12 months after initial merge
=> enough time to shake out remaining problems before next round of
enterprise distro kernel rebases
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-05 23:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 14:59 XFS status update for August 2010 Christoph Hellwig
2010-09-05 7:44 ` Willy Tarreau
2010-09-05 9:37 ` Michael Monnerie
2010-09-05 10:47 ` Willy Tarreau
2010-09-05 13:08 ` Dave Chinner
2010-09-05 18:56 ` Willy Tarreau
2010-09-05 23:36 ` Dave Chinner [this message]
2010-09-06 5:19 ` Willy Tarreau
2010-09-06 5:49 ` xfs mount/create options (was: XFS status update for August 2010) Michael Monnerie
2010-09-08 5:38 ` Michael Monnerie
2010-09-08 10:58 ` Dave Chinner
2010-09-08 13:38 ` Michael Monnerie
2010-09-08 14:51 ` Dave Chinner
2010-09-08 15:24 ` Emmanuel Florac
2010-09-08 23:34 ` Michael Monnerie
2010-09-08 23:30 ` Michael Monnerie
2010-09-09 7:27 ` Dave Chinner
2010-09-09 8:29 ` Michael Monnerie
2010-09-06 3:22 ` XFS status update for August 2010 Eric Sandeen
2010-09-06 5:10 ` Michael Monnerie
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=20100905233635.GW7362@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=w@1wt.eu \
--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