[Top] [All Lists]

Re: high load and xfsaild in d

To: linux-xfs@xxxxxxxxxxx
Subject: Re: high load and xfsaild in d
From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 23 Nov 2012 12:19:59 -0800
References: <sn23o9xkh3.ln2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20121123025624.GC32450@dastard> <uua3o9x9q5.ln2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20121123053913.GD32450@dastard>
User-agent: slrn/0.9.9p1 (Linux)
On 2012-11-23, Dave Chinner <david@xxxxxxxxxxxxx> 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?

>> 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.
(That's why I was so surprised--I'm not used to the RHEL kernel moving
so quickly!)


(try just my userid to email me)
see X- headers for PGP signature information

<Prev in Thread] Current Thread [Next in Thread>