From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Indefinite hang in reserve_metadata_bytes on kernel 3.18.3
Date: Thu, 29 Jan 2015 10:08:32 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.01.29.10.08.32@googlemail.com> (raw)
In-Reply-To: 868704D3-B79F-476F-A4CF-33C41274E6D4@opentable.com
On Thu, 29 Jan 2015 01:44:02 +0000, Steven Schlansker wrote:
[..snip..]
> The symptoms are an endlessly increasing stream of hung tasks and high
Please try 3.18.5 (-rc1 is good) which contains the following fix:
"workqueue: fix subtle pool management issue which can stall whole
worker_pool"
see: http://article.gmane.org/gmane.linux.kernel.stable/122074
No promises but it seems sufficiently causally related..
-h
next prev parent reply other threads:[~2015-01-29 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 1:44 Indefinite hang in reserve_metadata_bytes on kernel 3.18.3 Steven Schlansker
2015-01-29 10:08 ` Holger Hoffstätte [this message]
[not found] ` <54CA06A6.3070108@googlemail.com>
2015-01-29 22:50 ` Steven Schlansker
2015-01-30 10:02 ` Holger Hoffstätte
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=pan.2015.01.29.10.08.32@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).