From: "Chris Murphy" <lists@colorremedies.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-nvme@lists.infradead.org,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS error (device nvme1n1p2): bdev /dev/nvme0n1p2 errs: wr 37868055...
Date: Tue, 11 Nov 2025 11:56:37 -0500 [thread overview]
Message-ID: <e5a2b8b2-d4e5-42ce-9324-5748c5e078d4@app.fastmail.com> (raw)
In-Reply-To: <CAO9zADwMjaMp=TmgkBDHVFxdj5FVHtjTn_6qvFaTcAjpbaDSWg@mail.gmail.com>
On Mon, Nov 10, 2025, at 10:05 AM, Justin Piszcz wrote:
> Hello,
>
> I am using an ASUS Pro WS W680-ACE motherboard with 2 x Samsung SSD
> 990 PRO with Heatsink 4TB NVME SSDs with BTRFS R1. When a BTRFS scrub
> was kicked off this morning, suddenly BTRFS was noting errors for one
> of the drives. The system became unusable and I had to power cycle
> and re-run the scrub and everything is now OK. My question is what
> would cause this?
We'd have to see a complete dmesg at the time the problem occurred. If the same device holds system log files, seems like a pretty good chance none of it made it to persistent storage.
All we know is btrfs sees a bunch of dropped reads, writes, and flush requests. So it's not a btrfs error per se, though it affects btrfs. The issue is with the NVMe drive, its firmware, or a kernel nvme driver bug, or some combination of those.
--
Chris Murphy
next prev parent reply other threads:[~2025-11-11 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 15:05 Justin Piszcz
2025-11-11 16:56 ` Chris Murphy [this message]
2025-11-11 18:08 ` Chaitanya Kulkarni
2025-11-11 18:25 ` Justin Piszcz
2025-11-11 19:40 ` Chris Murphy
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=e5a2b8b2-d4e5-42ce-9324-5748c5e078d4@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®