From: Dave Chinner <david@fromorbit.com>
To: Jean-Tiare Le Bigot <jean-tiare.le-bigot@corp.ovh.com>
Cc: xfs@oss.sgi.com
Subject: Re: backport 7a29ac474a47eb8cf212b45917683ae89d6fa13b to stable ?
Date: Wed, 24 Feb 2016 09:45:55 +1100 [thread overview]
Message-ID: <20160223224555.GM25832@dastard> (raw)
In-Reply-To: <56CC852F.7010507@corp.ovh.com>
On Tue, Feb 23, 2016 at 05:13:35PM +0100, Jean-Tiare Le Bigot wrote:
> Hi,
>
> We've hit kernel hang related to XFS reclaim under heavy I/O load on a
> couple of storage servers using XFS over flashcache over a 3.13.y kernel.
>
> On the crash dumps, kthreadd is blocked, waiting for XFS to reclaim some
> memory but the related reclaim job is queued on a worker_pool stuck
> waiting for some I/O, itself depending on other jobs on other queues
> which would require additional threads to go forward. Unfortunately
> kthreadd is blocked.
> The host has plenty of memory (~128GB), about 80% of which being used
> for the page cache.
>
> It looks like this is fixed by commit
> 7a29ac474a47eb8cf212b45917683ae89d6fa13b.
That commit fixed a regression introduced, IIRC, in 3.19. The
problem it fixed didn't exist before then, so I doubt you are seeing
the problem that the above commit fixed. Perhaps you'd like to
describe your problem along with the stack traces, etc so we have
some idea of what you are trying to to fix?
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:[~2016-02-23 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:13 backport 7a29ac474a47eb8cf212b45917683ae89d6fa13b to stable ? Jean-Tiare Le Bigot
2016-02-23 22:45 ` Dave Chinner [this message]
2016-02-24 17:27 ` Jean-Tiare Le Bigot
2016-02-24 21:30 ` Dave Chinner
2016-02-25 16:45 ` Jean-Tiare Le Bigot
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=20160223224555.GM25832@dastard \
--to=david@fromorbit.com \
--cc=jean-tiare.le-bigot@corp.ovh.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