From: Dave Chinner <david@fromorbit.com>
To: Keith Keller <kkeller@wombat.san-francisco.ca.us>
Cc: linux-xfs@oss.sgi.com
Subject: Re: high load and xfsaild in d
Date: Fri, 23 Nov 2012 16:39:13 +1100 [thread overview]
Message-ID: <20121123053913.GD32450@dastard> (raw)
In-Reply-To: <uua3o9x9q5.ln2@goaway.wombat.san-francisco.ca.us>
On Thu, Nov 22, 2012 at 08:34:06PM -0800, Keith Keller wrote:
> On 2012-11-23, Dave Chinner <david@fromorbit.com> wrote:
> > That's a side effect of a minimal set of bug fixes that were needed
> > to avoid a load related log space hang. Those fixes disabled the
> > aild idling logic so the aild acts as a watchdog, so they wake up
> > every 50ms to check if there's anything to do. You'll find that
> > 3.0.x stable kernels have the same behaviour.
> >
> > The aild idling logic was re-enabled in mainstream kernels after the
> > root cause of the log space hangs was diagnosed and fixed, but I
> > can't see it ever being re-enabled in a CentOS 6.3 kernel....
>
> Thanks for the clarification, Dave. It sounds like I would need to
> either wait for this fix to hit the CentOS release kernel, or compile my
> own.
Do whatever you want - you might be waiting a while for CentOS to
fix it, though, because they don't fix user reported bugs. They just
repackage whatever Red Hat releases as RHEL.
TANSTAAFL.
> Do you know why I might not see this behavior on a different CentOS 6.x
> kernel?
>
> Linux xxxxxx 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug 24 01:07:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Because the log hang bug hadn't been fixed in that kernel.
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:[~2012-11-23 5:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 2:13 high load and xfsaild in d Keith Keller
2012-11-23 2:56 ` Dave Chinner
2012-11-23 4:34 ` Keith Keller
2012-11-23 5:39 ` Dave Chinner [this message]
2012-11-23 20:19 ` Keith Keller
2012-11-23 21:33 ` Dave Chinner
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=20121123053913.GD32450@dastard \
--to=david@fromorbit.com \
--cc=kkeller@wombat.san-francisco.ca.us \
--cc=linux-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