public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Kenneth R. Crudup" <kenny@panix.com>,
	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: Tue, 23 Nov 2021 16:27:33 -0700	[thread overview]
Message-ID: <b9c2681f-e63a-4d3b-913d-d8a75e2c2ea0@kernel.dk> (raw)
In-Reply-To: <b3ba57a7-d363-9c17-c4be-9dbe86875@panix.com>

On 11/23/21 2:05 PM, Kenneth R. Crudup wrote:
> 
> (Please forgive the SPAMmy nature of the To: list; I'm not exactly sure whose
> subsystem this issue belongs to, so please trim as appropriate).
> 
> I've got a Kioxia NVMe SSD on my Dell XPS-7390 2-in-1 running an i7-1065G7 CPU
> with 32GB RAM.  If you need more info (and I suspect so), please let me know.
> 
> I'm sorry I don't have a better description of the problem, but I run Linus'
> master branch (and sometimes I weed out problems like this). I'm current as of
> his commit 1360572566 (the 5.16-rc2 tag).
> 
> For about two weeks now every now and then my block/NVMe/...? subsystem comes to
> a total halt on writes, and I get a system that can no longer issue writes
> (reads/pageins still seem to work) until I reboot. SysRq-S/U/B still leaves a
> dirty ext4 filesystem requring recovery on reboot.
> 
> It happens at random- twice today as a matter of fact- and there doesn't seem to
> be any particular action that causes it:

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.

I'll take a look at this, but most likely not until start next week...

-- 
Jens Axboe



  parent reply	other threads:[~2021-11-23 23:27 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 [this message]
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

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=b9c2681f-e63a-4d3b-913d-d8a75e2c2ea0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox