From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216007] XFS hangs in iowait when extracting large number of files
Date: Sun, 05 Jun 2022 07:51:13 +0000 [thread overview]
Message-ID: <bug-216007-201763-uYTTdxLIlY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216007-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216007
--- Comment #25 from Jordi (clockwork80@gmail.com) ---
I have applied the patch on vanilla 5.18.1 kernel and the issue is not resolved
on ext4.
Here's the output of dmesg:
[Sun Jun 5 09:44:51 2022] sysrq: Show Blocked State
[Sun Jun 5 09:44:51 2022] task:kworker/u24:11 state:D stack: 0 pid: 145
ppid: 2 flags:0x00004000
[Sun Jun 5 09:44:51 2022] Workqueue: writeback wb_workfn (flush-8:32)
[Sun Jun 5 09:44:51 2022] Call Trace:
[Sun Jun 5 09:44:51 2022] <TASK>
[Sun Jun 5 09:44:51 2022] __schedule+0x26d/0xe80
[Sun Jun 5 09:44:51 2022] ? __blk_flush_plug+0xe1/0x140
[Sun Jun 5 09:44:51 2022] schedule+0x46/0xa0
[Sun Jun 5 09:44:51 2022] io_schedule+0x3d/0x60
[Sun Jun 5 09:44:51 2022] blk_mq_get_tag+0x115/0x2b0
[Sun Jun 5 09:44:51 2022] ? destroy_sched_domains_rcu+0x20/0x20
[Sun Jun 5 09:44:51 2022] __blk_mq_alloc_requests+0x157/0x290
[Sun Jun 5 09:44:51 2022] blk_mq_submit_bio+0x188/0x520
[Sun Jun 5 09:44:51 2022] submit_bio_noacct_nocheck+0x252/0x2a0
[Sun Jun 5 09:44:51 2022] ext4_io_submit+0x1b/0x40
[Sun Jun 5 09:44:51 2022] ext4_writepages+0x4fc/0xe80
[Sun Jun 5 09:44:51 2022] ? ata_qc_issue+0x101/0x1b0
[Sun Jun 5 09:44:51 2022] ? __ata_scsi_queuecmd+0x17a/0x380
[Sun Jun 5 09:44:51 2022] ? update_load_avg+0x77/0x610
[Sun Jun 5 09:44:51 2022] do_writepages+0xbc/0x1a0
[Sun Jun 5 09:44:51 2022] ? __schedule+0x275/0xe80
[Sun Jun 5 09:44:51 2022] __writeback_single_inode+0x2c/0x180
[Sun Jun 5 09:44:51 2022] writeback_sb_inodes+0x204/0x490
[Sun Jun 5 09:44:51 2022] __writeback_inodes_wb+0x47/0xd0
[Sun Jun 5 09:44:51 2022] wb_writeback.isra.0+0x15d/0x1a0
[Sun Jun 5 09:44:51 2022] wb_workfn+0x23d/0x3a0
[Sun Jun 5 09:44:51 2022] process_one_work+0x1b0/0x300
[Sun Jun 5 09:44:51 2022] worker_thread+0x48/0x3c0
[Sun Jun 5 09:44:51 2022] ? rescuer_thread+0x380/0x380
[Sun Jun 5 09:44:51 2022] kthread+0xd4/0x100
[Sun Jun 5 09:44:51 2022] ? kthread_complete_and_exit+0x20/0x20
[Sun Jun 5 09:44:51 2022] ret_from_fork+0x22/0x30
[Sun Jun 5 09:44:51 2022] </TASK>
[Sun Jun 5 09:44:51 2022] task:tar state:D stack: 0 pid:11576
ppid: 11566 flags:0x00000000
[Sun Jun 5 09:44:51 2022] Call Trace:
[Sun Jun 5 09:44:51 2022] <TASK>
[Sun Jun 5 09:44:51 2022] __schedule+0x26d/0xe80
[Sun Jun 5 09:44:51 2022] ? __mod_timer+0x1c2/0x3b0
[Sun Jun 5 09:44:51 2022] schedule+0x46/0xa0
[Sun Jun 5 09:44:51 2022] schedule_timeout+0x7c/0xf0
[Sun Jun 5 09:44:51 2022] ? fprop_fraction_percpu+0x2b/0x70
[Sun Jun 5 09:44:51 2022] ? init_timer_key+0x30/0x30
[Sun Jun 5 09:44:51 2022] io_schedule_timeout+0x47/0x70
[Sun Jun 5 09:44:51 2022] balance_dirty_pages_ratelimited+0x235/0xa10
[Sun Jun 5 09:44:51 2022] generic_perform_write+0x142/0x200
[Sun Jun 5 09:44:51 2022] ext4_buffered_write_iter+0x76/0x100
[Sun Jun 5 09:44:51 2022] new_sync_write+0x104/0x180
[Sun Jun 5 09:44:51 2022] vfs_write+0x1e6/0x270
[Sun Jun 5 09:44:51 2022] ksys_write+0x5a/0xd0
[Sun Jun 5 09:44:51 2022] do_syscall_64+0x3b/0x90
[Sun Jun 5 09:44:51 2022] entry_SYSCALL_64_after_hwframe+0x44/0xae
[Sun Jun 5 09:44:51 2022] RIP: 0033:0x7f994fe7c483
[Sun Jun 5 09:44:51 2022] RSP: 002b:00007ffe79956648 EFLAGS: 00000246
ORIG_RAX: 0000000000000001
[Sun Jun 5 09:44:51 2022] RAX: ffffffffffffffda RBX: 0000000000001084 RCX:
00007f994fe7c483
[Sun Jun 5 09:44:51 2022] RDX: 0000000000001084 RSI: 000055f5bb5a9a00 RDI:
0000000000000003
[Sun Jun 5 09:44:51 2022] RBP: 000055f5bb5a9a00 R08: 00007f994fe7c260 R09:
0000000000000000
[Sun Jun 5 09:44:51 2022] R10: 00000000000001a4 R11: 0000000000000246 R12:
0000000000000003
[Sun Jun 5 09:44:51 2022] R13: 0000000000000003 R14: 000055f5bb5b5320 R15:
000055f5bb5a9a00
[Sun Jun 5 09:44:51 2022] </TASK>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-06-05 7:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 11:56 [Bug 216007] New: XFS hangs in iowait when extracting large number of files bugzilla-daemon
2022-05-20 11:56 ` [Bug 216007] " bugzilla-daemon
2022-05-20 20:46 ` bugzilla-daemon
2022-05-20 23:05 ` [Bug 216007] New: " Dave Chinner
2022-05-20 23:05 ` [Bug 216007] " bugzilla-daemon
2022-05-21 5:14 ` bugzilla-daemon
2022-05-21 22:31 ` Dave Chinner
2022-05-21 22:31 ` bugzilla-daemon
2022-05-23 8:29 ` bugzilla-daemon
2022-05-23 8:31 ` bugzilla-daemon
2022-05-23 10:02 ` bugzilla-daemon
2022-05-23 10:28 ` bugzilla-daemon
2022-05-24 7:54 ` bugzilla-daemon
2022-05-24 10:00 ` bugzilla-daemon
2022-05-24 10:49 ` bugzilla-daemon
2022-05-24 10:52 ` bugzilla-daemon
2022-05-24 10:53 ` bugzilla-daemon
2022-05-24 11:21 ` bugzilla-daemon
2022-05-24 11:48 ` bugzilla-daemon
2022-05-24 11:49 ` bugzilla-daemon
2022-05-25 17:13 ` bugzilla-daemon
2022-05-26 4:04 ` bugzilla-daemon
2022-05-26 8:51 ` bugzilla-daemon
2022-05-26 9:16 ` bugzilla-daemon
2022-05-26 10:26 ` bugzilla-daemon
2022-05-26 10:37 ` bugzilla-daemon
2022-06-04 16:25 ` bugzilla-daemon
2022-06-05 7:51 ` bugzilla-daemon [this message]
2022-06-06 7:49 ` bugzilla-daemon
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=bug-216007-201763-uYTTdxLIlY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@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).