From: CAI Qian <caiqian@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Steve Best <sbest@redhat.com>, xfs@oss.sgi.com
Subject: Re: possible fsync02() xfs slowness regression on power7
Date: Fri, 1 Mar 2013 04:20:18 -0500 (EST) [thread overview]
Message-ID: <220575861.7590457.1362129618880.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20130228115410.GN5551@dastard>
----- 原始邮件 -----
> 发件人: "Dave Chinner" <david@fromorbit.com>
> 收件人: "CAI Qian" <caiqian@redhat.com>
> 抄送: xfs@oss.sgi.com, "Steve Best" <sbest@redhat.com>
> 发送时间: 星期四, 2013年 2 月 28日 下午 7:54:10
> 主题: Re: possible fsync02() xfs slowness regression on power7
>
> On Thu, Feb 28, 2013 at 04:28:35AM -0500, CAI Qian wrote:
> > This LTP test starting to fail using the latest upstream kernel on
> > one of the power7
> > systems here, http://tinyurl.com/bngwouj
> >
> > # ./fsync02
> > fsync02 1 TFAIL : fsync took too long: 252.000000 seconds;
> > max_block: 214
> >
> > When it is working, the test is almost returned immediately. The
> > bisecting so far
> > indicated that one or a few of the following could be culprits.
> >
> > # git log --pretty=oneline
> > 498f7f505dc79934c878c7667840c50c64f232fc..b199c8a4ba11879df87daad496ceee41fdc6aa82
>
> They are all patches committed more than 2 years ago, and none of
> them are platform specific. This sounds more like a machine specific
> issue than a platform specific problem (i.e. lots of RAM, slow,
> slow disk).
>
> In future when reporting a bug, please tell use hardware you are
> using as per:
>
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
>
> Given that this is a sparse file test that repeatedly extends the
> file, this is the likely culprit:
>
> > 055388a3188f56676c21e92962fc366ac8b5cb72 xfs: dynamic speculative
> > EOF preallocation
Yes, you are right, just confirmed it. Nice catch!
>
> And this commit in 3.9-rc1:
>
> a1e16c2 xfs: limit speculative prealloc size on sparse files
Just back-ported it and running at the moment and will let you know. Thanks Dave.
>
> should fix the problem. Please confirm these commits are the cause
> and the fix respectively....
>
> 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:[~2013-03-01 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <130819766.6999797.1362043338279.JavaMail.root@redhat.com>
2013-02-28 9:28 ` possible fsync02() xfs slowness regression on power7 CAI Qian
2013-02-28 11:54 ` Dave Chinner
2013-03-01 9:20 ` CAI Qian [this message]
2013-03-04 4:23 ` CAI Qian
2013-03-04 5:55 ` Dave Chinner
2013-03-04 6:14 ` CAI Qian
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=220575861.7590457.1362129618880.JavaMail.root@redhat.com \
--to=caiqian@redhat.com \
--cc=david@fromorbit.com \
--cc=sbest@redhat.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