From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Johannes Ernst <johannes.ernst@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Hanging after frequent use of systemd-nspawn --ephemeral
Date: Mon, 15 Jan 2018 09:34:56 +0800 [thread overview]
Message-ID: <618575b8-419e-3d09-add0-e42d2c0bb7b2@gmx.com> (raw)
In-Reply-To: <C376D549-BE55-4B02-A681-39180F63E372@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1365 bytes --]
On 2018年01月15日 08:58, Johannes Ernst wrote:
>>> INFO: task systemd-journal:20876 blocked for more than 120 seconds.
>>> [ 5037.962603] Tainted: G C O 4.14.9-1-ARCH #1
>>> [ 5037.962609] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>>> [ 5037.962616] systemd-journal D 0 20876 20860 0x00000100
>>> [ 5037.962622] Call Trace:
>>> [ 5037.962635] ? __schedule+0x290/0x890
>>> [ 5037.962640] ? __slab_free+0x14e/0x300
>>> [ 5037.962645] ? _copy_to_iter+0x8f/0x3d0
>>> [ 5037.962651] schedule+0x2f/0x90
>>> [ 5037.962704] btrfs_tree_read_lock+0xb6/0x100 [btrfs]
>>
>> Still some tree write is blocking all incoming read.
>>
>> BTW, did your tests include any send and relocation operations?
>>
>> IIRC there is a bug that makes send and relocation (I'm not sure though)
>> will cause similar problem.
>
> No. I’m doing nothing btrfs-specific at all, it’s just whatever systemd-nspawn —ephemeral does.
So, only systemd-nspwan --ephemeral, and nothing else at all?
Even nothing happened inside the container?
Thanks,
Qu
>
> Cheers,
>
>
>
> Johannes.--
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2018-01-15 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 1:36 Hanging after frequent use of systemd-nspawn --ephemeral Johannes Ernst
2018-01-14 2:27 ` Qu Wenruo
2018-01-14 16:30 ` Duncan
2018-01-14 20:17 ` Johannes Ernst
2018-01-15 0:48 ` Qu Wenruo
2018-01-15 0:58 ` Johannes Ernst
2018-01-15 1:34 ` Qu Wenruo [this message]
2018-01-15 1:47 ` Johannes Ernst
2018-01-15 1:55 ` Qu Wenruo
2018-01-14 20:18 ` Johannes Ernst
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=618575b8-419e-3d09-add0-e42d2c0bb7b2@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=johannes.ernst@gmail.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).