From: "Kenneth R. Crudup" <kenny@panix.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-nvme@lists.infradead.org,
shinichiro.kawasaki@wdc.com
Subject: Re: Write I/O queue hangup at random on recent Linus' kernels
Date: Thu, 2 Dec 2021 07:37:26 -0800 (PST) [thread overview]
Message-ID: <a2eb227a-a4dc-e4e7-d3ea-567778bfc9c0@panix.com> (raw)
In-Reply-To: <4429eed8-b9b9-6943-f76-6ea38d695248@panix.com>
On Thu, 2 Dec 2021, Kenneth R. Crudup wrote:
> $ egrep -r . $(sudo find /sys/block/*/ -name inflight )
>
> ... but they were all zeros.
... and similarly:
----
$ sudo egrep -r . $(sudo find /sys/kernel/debug/block/ -name inflight)
/sys/kernel/debug/block/mmcblk0/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/mmcblk0/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/mmcblk0/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/sda/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/sda/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/sda/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/nvme0n1/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/nvme0n1/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/nvme0n1/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop7/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop7/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop7/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop6/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop6/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop6/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop5/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop5/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop5/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop4/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop4/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop4/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop3/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop3/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop3/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop2/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop2/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop2/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop1/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop1/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop1/rqos/wbt/inflight:2: inflight 0
/sys/kernel/debug/block/loop0/rqos/wbt/inflight:0: inflight 0
/sys/kernel/debug/block/loop0/rqos/wbt/inflight:1: inflight 0
/sys/kernel/debug/block/loop0/rqos/wbt/inflight:2: inflight 0
----
(... but just now, I got a delayed popup from my UI, which then went back to
being unresponsive again)
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
prev parent reply other threads:[~2021-12-02 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 21:05 Write I/O queue hangup at random on recent Linus' kernels Kenneth R. Crudup
2021-11-23 23:23 ` Kenneth R. Crudup
2021-11-23 23:27 ` Jens Axboe
2021-11-23 23:35 ` Kenneth R. Crudup
2021-11-25 21:05 ` Kenneth R. Crudup
2021-11-25 21:07 ` Jens Axboe
2021-11-25 21:11 ` Kenneth R. Crudup
2021-11-26 16:53 ` Jens Axboe
2021-11-26 17:09 ` Kenneth R. Crudup
2021-11-26 17:58 ` Kenneth R. Crudup
2021-11-26 18:10 ` Jens Axboe
2021-11-26 18:20 ` Kenneth R. Crudup
2021-11-26 18:41 ` Jens Axboe
2021-11-28 0:11 ` Kenneth R. Crudup
2021-11-28 14:50 ` Jens Axboe
2021-12-02 15:13 ` Kenneth R. Crudup
2021-12-02 15:37 ` Kenneth R. Crudup [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=a2eb227a-a4dc-e4e7-d3ea-567778bfc9c0@panix.com \
--to=kenny@panix.com \
--cc=axboe@kernel.dk \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.