From: Nikolay Borisov <nborisov@suse.com>
To: Adam Borowski <kilobyte@angband.pl>, linux-btrfs@vger.kernel.org
Subject: Re: hang in btrfs_async_reclaim_metadata_space
Date: Sun, 7 Jan 2018 13:17:19 +0200 [thread overview]
Message-ID: <80c373ee-1bd7-d59b-a252-04309c8b0210@suse.com> (raw)
In-Reply-To: <20180106051059.kpultyyfhgxjowf5@angband.pl>
On 6.01.2018 07:10, Adam Borowski wrote:
> Hi!
> I got a reproducible infinite hang, reliably triggered by the testsuite of
> "flatpak"; fails on at least 4.15-rc6, 4.9.75, and on another machine with
> Debian's 4.14.2-1.
>
> [580632.355107] INFO: task kworker/u8:2:11105 blocked for more than 120 seconds.
> [580632.355120] Not tainted 4.14.0-1-amd64 #1 Debian 4.14.2-1
> [580632.355124] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [580632.355129] kworker/u8:2 D 0 11105 2 0x80000000
> [580632.355176] Workqueue: events_unbound btrfs_async_reclaim_metadata_space [btrfs]
> [580632.355179] Call Trace:
> [580632.355192] __schedule+0x28e/0x880
> [580632.355196] schedule+0x2c/0x80
> [580632.355200] wb_wait_for_completion+0x64/0x90
> [580632.355205] ? finish_wait+0x80/0x80
> [580632.355207] __writeback_inodes_sb_nr+0xa1/0xd0
> [580632.355210] writeback_inodes_sb_nr+0x10/0x20
> [580632.355235] flush_space+0x3ed/0x520 [btrfs]
> [580632.355238] ? pick_next_task_fair+0x158/0x590
> [580632.355242] ? __switch_to+0x1f3/0x460
> [580632.355267] btrfs_async_reclaim_metadata_space+0xf6/0x4a0 [btrfs]
> [580632.355278] process_one_work+0x198/0x390
> [580632.355281] worker_thread+0x35/0x3c0
> [580632.355284] kthread+0x125/0x140
> [580632.355287] ? process_one_work+0x390/0x390
> [580632.355289] ? kthread_create_on_node+0x70/0x70
> [580632.355292] ? SyS_exit_group+0x14/0x20
> [580632.355295] ret_from_fork+0x25/0x30
>
> The machines are distinct enough that this probably should happen
> everywhere:
>
> AMD Phenom2, SSD, noatime,compress=lzo,space_cache=v2
> Intel Braswell, rust, noatime,autodefrag,space_cache=v2
Provide output of echo w > /proc/sysrq-trigger when the hang happens.
>
>
> Meow!
>
next prev parent reply other threads:[~2018-01-07 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 5:10 hang in btrfs_async_reclaim_metadata_space Adam Borowski
2018-01-07 11:17 ` Nikolay Borisov [this message]
2018-01-11 3:03 ` Adam Borowski
2018-01-11 8:05 ` Nikolay Borisov
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=80c373ee-1bd7-d59b-a252-04309c8b0210@suse.com \
--to=nborisov@suse.com \
--cc=kilobyte@angband.pl \
--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).