From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Chris Mason <clm@fb.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: deadlock with btrfs heavy i/o and kswapd
Date: Tue, 27 Sep 2016 08:41:06 +0200 [thread overview]
Message-ID: <0cd5ff1d-f3ef-ccfb-4460-884470dab199@profihost.ag> (raw)
In-Reply-To: <8116272d-6c30-431a-c3e1-781b17bea2c6@fb.com>
Hi Chris,
today i had this again. But i can't see any stack traces. I just see.
INFO: kworker/u128:5:24301 blocked for more than 120 seconds.
...
INFO: kworker/u128:5:24301 blocked for more than 120 seconds.
...
INFO: task mysqld:929 blocked for more ...
...
sysrq w just prints:
sysrq: SysRq: Show Blcoked State
but nothing more.
Stefan
Am 22.09.2016 um 16:28 schrieb Chris Mason:
>
>
> On 09/22/2016 02:41 AM, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> i always encounter btrfs deadlocks / hung tasks, when i have a lot of
>> cached mem and i'm doing heavy rsync --inplace operations in my system
>> from btrfs zlib compressed disk A to btrfs zlib compressed disk B.
>>
>> The last output i see in this case is kswapd0 running for a long time at
>> 100% cpu. Then the whole system get's stuck. I cannot connect to ssh
>> anymore but the kernel still prints hung tasks every few minutes.
>>
>> May be relevant the system has NO swap.
>>
>> vm.vfs_cache_pressure = 100
>> vm.swappiness = 50
>
> Are you able to capture the stack dumps? A sysrq-w would really help.
>
> -chris
>
prev parent reply other threads:[~2016-09-27 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 6:41 deadlock with btrfs heavy i/o and kswapd Stefan Priebe - Profihost AG
2016-09-22 14:28 ` Chris Mason
2016-09-26 6:59 ` Stefan Priebe - Profihost AG
2016-09-27 6:41 ` Stefan Priebe - Profihost AG [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=0cd5ff1d-f3ef-ccfb-4460-884470dab199@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=clm@fb.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).