From: Jens Axboe <axboe@kernel.dk>
To: "Kenneth R. Crudup" <kenny@panix.com>
Cc: linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: Write I/O queue hangup at random on recent Linus' kernels
Date: Thu, 25 Nov 2021 14:07:29 -0700 [thread overview]
Message-ID: <17206ea6-506d-b1de-09e8-c935ff308bd6@kernel.dk> (raw)
In-Reply-To: <be6a783-97db-c3bf-b16f-e8c62b14755d@panix.com>
On 11/25/21 2:05 PM, Kenneth R. Crudup wrote:
>
> On Tue, 23 Nov 2021, Jens Axboe wrote:
>
>> It looks like some missed accounting. You can just disable wbt for now, would
>> be a useful data point to see if that fixes it. Just do:
>
>> echo 0 > /sys/block/nvme0n1/queue/wbt_lat_usec
>
>> and that will disable writeback throttling on that device.
>
> It's been about 48 hours and haven't seen the issue since doing this.
Great, thanks for verifying. From your report 5.16-rc2 has the issue, is
5.15 fine?
--
Jens Axboe
next prev parent reply other threads:[~2021-11-25 21:11 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 [this message]
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
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=17206ea6-506d-b1de-09e8-c935ff308bd6@kernel.dk \
--to=axboe@kernel.dk \
--cc=kenny@panix.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 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.