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: Sat, 24 Nov 2012 08:33:50 +1100 [thread overview]
Message-ID: <20121123213350.GL32450@dastard> (raw)
In-Reply-To: <fc25o9xgfg.ln2@goaway.wombat.san-francisco.ca.us>
On Fri, Nov 23, 2012 at 12:19:59PM -0800, Keith Keller wrote:
> On 2012-11-23, Dave Chinner <david@fromorbit.com> wrote:
> >
> > 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.
>
> Yes, that's why I was asking--I was wondering whether it is safe to wait
> for what could be some time for a) RHEL to decide to patch (if they do
> so at all), b) RHEL to patch, and c) CentOS to patch. IOW, is the high
> load the only likely symptom of the originail aild patch, or are there
> potentially other problems, such as performance degradation that I
> haven't seen yet, that would make waiting for CentOS unwise?
There is no side effect other than the load. There are not
performance issues with the ailds behaving like this.
> >> 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.
>
> This actually gives me some optimism that RHEL might introduce a new
> kernel sooner rather than later--that kernel wasn't all that long ago,
> and there have been quite a few (mostly unrelated) patches since.
Doubt it. Given that I'm the RHEL XFS maintainer....
> (That's why I was so surprised--I'm not used to the RHEL kernel moving
> so quickly!)
What, you're not used to having serious bugs fixed quickly? That's
why people pay for RHEL...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-11-23 21:31 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
2012-11-23 20:19 ` Keith Keller
2012-11-23 21:33 ` Dave Chinner [this message]
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=20121123213350.GL32450@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 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.