From: Keith Busch <kbusch@kernel.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-nvme@lists.infradead.org, linux-raid@vger.kernel.org,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1)
Date: Mon, 1 Dec 2025 19:47:15 -0700 [thread overview]
Message-ID: <aS5TM30PizKtz_hW@kbusch-mbp> (raw)
In-Reply-To: <CAO9zADzUZYzM=xkvHPXepQP_+6V0f4__yroPNV6feyPB27Ju=Q@mail.gmail.com>
On Mon, Dec 01, 2025 at 09:13:01AM -0500, Justin Piszcz wrote:
> Nice, I was not aware of this, thanks! As this issue appears to
> affect different consumer-level NVME drives, any efforts to address
> the quirks in various NVME drives to restart the device while keeping
> the volume intact would be awesome if it is possible to- get that
> point in the future.
Various consumer NVMe's use 3rd party controllers, so maybe that's the
common denominator. There aren't very many to choose from.
Anyway, the suggestion won't fix random IO stalls when the situation
happens, but if it is successful, it should keep the volume in an
optimal state, albeit with exceptionally high latency during the
recovery window.
next prev parent reply other threads:[~2025-12-02 2:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 14:42 WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1) Justin Piszcz
2025-11-25 14:48 ` Dr. David Alan Gilbert
2025-12-01 14:09 ` Justin Piszcz
2025-11-25 14:56 ` Keith Busch
2025-12-01 14:13 ` Justin Piszcz
2025-12-02 2:47 ` Keith Busch [this message]
2025-11-25 15:19 ` Dragan Milivojević
2025-11-25 16:57 ` Paul Rolland
2025-12-08 13:37 ` Sinisa
2025-11-25 22:37 ` Jani Partanen
2025-12-01 14:14 ` Justin Piszcz
2025-12-08 8:43 ` Brad Campbell
2025-11-25 18:25 ` Wol
2025-11-26 0:15 ` David Sterba
2025-11-26 12:51 ` Roger Heflin
2025-12-01 14:16 ` Justin Piszcz
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=aS5TM30PizKtz_hW@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@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