From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 219166] ext4 hang when setting echo noop > /sys/block/sda/queue/scheduler
Date: Sat, 17 Aug 2024 12:36:41 +0000 [thread overview]
Message-ID: <bug-219166-13602-5utlJeiM8g@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219166-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219166
--- Comment #6 from Richard W.M. Jones (rjones@redhat.com) ---
Yes I can reproduce this inside a software emulated VM with another 6.11.0
Fedora kernel. I will bisect this later, but for now reproduction instructions
are given below.
(1) Install a Fedora 40 virtual machine. I used the command below but other
ways are available:
virt-builder fedora-40 --size=10G --root-password=password:123456
(2) Run the VM in qemu with software emulation (TCG):
qemu-system-x86_64 -machine accel=tcg -cpu qemu64 -m 4096 -drive
file=/var/tmp/fedora-40.qcow2,format=qcow2,if=virtio
(3) Inside the VM, log in as root/123456, install fio, and update the kernel:
dnf install fedora-repos-rawhide
dnf install fio
dnf update kernel
reboot
(should upgrade to 6.11.0 and boot into that kernel).
(4) Inside the VM, in one terminal run:
while true; do echo noop > /sys/block/sda/queue/scheduler 2>/dev/null ; done
(5) Inside the VM, in another terminal run fio with the following config or
similar:
[global]
name=fio-rand-write
filename=/root/fio-rand-write
rw=randwrite
bs=4K
numjobs=4
time_based
runtime=1h
group_reporting
[file1]
size=1G
ioengine=libaio
iodepth=64
(6) After a while the fio process ETA will start counting up (since one or more
threads have got stuck and are not making progress). Also logging in is
problematic and many common commands like 'dmesg' or 'ps' hang. I could only
recover by rebooting.
--
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:[~2024-08-17 12:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 7:43 [Bug 219166] New: ext4 hang when setting echo noop > /sys/block/sda/queue/scheduler bugzilla-daemon
2024-08-16 16:40 ` [Bug 219166] " bugzilla-daemon
2024-08-16 17:06 ` bugzilla-daemon
2024-08-16 20:36 ` bugzilla-daemon
2024-08-16 20:51 ` bugzilla-daemon
2024-08-17 10:22 ` bugzilla-daemon
2024-08-17 12:36 ` bugzilla-daemon [this message]
2024-08-17 12:38 ` bugzilla-daemon
2024-08-17 12:41 ` bugzilla-daemon
2024-08-17 13:58 ` bugzilla-daemon
2024-08-20 15:33 ` bugzilla-daemon
2024-08-20 15:33 ` [Bug 219166] occasional block layer hang when setting 'echo noop > /sys/block/sda/queue/scheduler' bugzilla-daemon
2024-09-05 1:04 ` bugzilla-daemon
2024-09-05 7:25 ` bugzilla-daemon
2024-09-05 9:32 ` bugzilla-daemon
2024-09-06 19:46 ` bugzilla-daemon
2024-09-06 20:28 ` bugzilla-daemon
2024-09-06 20:32 ` bugzilla-daemon
2024-09-07 7:49 ` bugzilla-daemon
2024-09-07 11:09 ` bugzilla-daemon
2024-09-07 11:10 ` bugzilla-daemon
2024-09-18 8:36 ` 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-219166-13602-5utlJeiM8g@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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).