From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org,
"p.herz@profihost.ag >> Philipp Herz - Profihost AG"
<p.herz@profihost.ag>,
stable@vger.kernel.org
Subject: Re: Call trace in ext4_es_lru_add on 3.10 stable
Date: Tue, 23 Sep 2014 09:50:25 +0200 [thread overview]
Message-ID: <54212641.9010808@profihost.ag> (raw)
In-Reply-To: <20140922202004.GF4572@thunk.org>
Am 22.09.2014 um 22:20 schrieb Theodore Ts'o:
> On Mon, Sep 22, 2014 at 08:29:54PM +0200, Stefan Priebe wrote:
>> Hi,
>> Am 22.09.2014 18:47, schrieb Theodore Ts'o:
>>> On Mon, Sep 22, 2014 at 08:56:23AM +0200, Stefan Priebe wrote:
>>>>> That's not the whole message; you just weren't able to capture it all.
>>>>> How are you capturing these messages, by the way? Serial console?
>>>>
>>>> Sorry this was an incomplete copy and paste by me.
>>>>
>>>> Here is the complete output:
>>>> [1578544.839610] BUG: soft lockup - CPU#7 stuck for 22s! [mysqld:29281]
>>>> [1578544.893450] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4
>>>
>>> OK, thanks, this is a known bug, where when ext4 is under heavy memory
>>> pressure, we can end up stalling in reclaim. This message indicates
>>> that the system got stalled for 22 seconds, which is not good, since
>>> it impacts the interactivity of your system, and increases the
>>> long-tail latency of requests to servers running on your system, but
>>> it doesn't cause any data loss or will cause any of your processes to
>>> crash or otherwise stop functioning (except for temporarily).
>>>
>>> It's something that we are working on, and there are patches which
>>> Zheng Liu submitted that still need a bit of polishing, but I hope to
>>> have it addressed soon.
>>
>> Thanks for your feedback. Will those patches go to stable? Any link to
>> those patches?
>
> I'm not sure they will go to Stable when they are ready, because the
> patches are somewhat complex and so they may not apply cleanly to much
> older kernels.
>
> The patches under discussion (some have been applied, others hae been
> waiting for some requested changes) can be found here:
>
> http://patchwork.ozlabs.org/patch/377720
> http://patchwork.ozlabs.org/patch/377721
> http://patchwork.ozlabs.org/patch/377722
> http://patchwork.ozlabs.org/patch/377723
> http://patchwork.ozlabs.org/patch/377724
> http://patchwork.ozlabs.org/patch/377725
> http://patchwork.ozlabs.org/patch/377727
hui that's a lot. Are they ALL needed to fix this? No workaround
possible? What will Redhat do with their 3.10 RHEL 7 kernel?
Stefan
next prev parent reply other threads:[~2014-09-23 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 13:08 Call trace in ext4_es_lru_add on 3.10 stable Stefan Priebe - Profihost AG
2014-09-18 19:21 ` Theodore Ts'o
2014-09-18 19:29 ` Stefan Priebe
2014-09-18 19:43 ` Theodore Ts'o
2014-09-22 6:56 ` Stefan Priebe
2014-09-22 16:47 ` Theodore Ts'o
2014-09-22 18:29 ` Stefan Priebe
2014-09-22 20:20 ` Theodore Ts'o
2014-09-23 7:50 ` Stefan Priebe - Profihost AG [this message]
2014-09-23 9:42 ` Jan Kara
2014-09-23 12:23 ` Stefan Priebe
2014-09-23 14:43 ` Jan Kara
2014-11-26 8:06 ` Stefan Priebe - Profihost AG
2014-11-26 8:25 ` Jan Kara
2014-11-26 10:28 ` Stefan Priebe - Profihost AG
2014-11-26 10:38 ` Jan Kara
2014-11-26 15:11 ` Stefan Priebe - Profihost AG
2014-11-26 20:26 ` Jan Kara
2014-11-26 20:33 ` Stefan Priebe
2014-12-04 15:06 ` Stefan Priebe - Profihost AG
2014-12-04 18:35 ` Jan Kara
2014-12-15 9:48 ` Stefan Priebe - Profihost AG
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=54212641.9010808@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=linux-ext4@vger.kernel.org \
--cc=p.herz@profihost.ag \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).