From: David Chinner <dgc@sgi.com>
To: Bond Masuda <bond.masuda@jlbond.com>
Cc: xfs@oss.sgi.com
Subject: Re: performance problems with XFS and Linux kernel 2.6.24.4
Date: Tue, 8 Apr 2008 08:01:06 +1000 [thread overview]
Message-ID: <20080407220106.GF108924158@sgi.com> (raw)
In-Reply-To: <007001c898f5$cae2f4a0$60a8dde0$@masuda@jlbond.com>
On Mon, Apr 07, 2008 at 02:24:41PM -0700, Bond Masuda wrote:
> Hi,
>
> I am aware of the change regarding barrier/nobarrier in 2.6.17 and above.
> However, the performance hit I'm seeing is very severe and much worse than
> what I was seeing in 2.6.17 (bundled with latest updates in Fedora Core 4).
>
> I'm currently running Fedora 8 with 2.6.24.4-64.fc8. If I remove nobarrier
> mount option, it takes seconds just to write few megabytes and the system
> becomes very very sluggish. On 2.6.17 (Fedora 4) without the nobarrier
> option it was still usable.
Doesn't sound like a barrier problem.
> The XFS file system is about 900GB, if that matters.
>
> Is this a known problem?
<shrug>
> How can I gather more information to figure out
> exactly what is going on?
Start with what your hardware is, what your storage config is, output
of 'xfs_info <mtpt>', the log of your test (complete output) on working
and non-working kernels, etc.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-07 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 21:24 performance problems with XFS and Linux kernel 2.6.24.4 Bond Masuda
2008-04-07 22:01 ` David Chinner [this message]
2008-05-07 15:36 ` Is this XFS problem or something else? : xfs_trans_read_buf error 5 buf count 4096 Bond Masuda
2008-05-07 15:51 ` Eric Sandeen
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=20080407220106.GF108924158@sgi.com \
--to=dgc@sgi.com \
--cc=bond.masuda@jlbond.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.