public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS error count 754 after reboot on Debian kernel 6.12.17
Date: Sun, 23 Mar 2025 00:44:22 +1100	[thread overview]
Message-ID: <3349404.aeNJFYEL58@xev> (raw)

[/dev/sdd1].write_io_errs    753
[/dev/sdd1].read_io_errs     1

I have a test system which has a strange problem where the BTRFS error count 
on one device (out of four) goes to 754 after a reboot.

There are no BTRFS errors in the kernel message log after booting up.  There 
are no log entries in /var/log/kern.log about BTRFS issues.  When I look at 
the console as it's shutting down I don't see any errors being logged, so 
either there are no errors logged or there are 753 errors logged in the final 
split second before power off or reboot so that I don't even see them.

This is repeatable and it's 754 every time.

After I get the error I remove the device from the array and add it again.  I 
can run it for days without problem with data being written to that device and 
read from it without error.

But when I reboot it says 754 errors.  When I swapped that device with another 
one in a different drive bay the same device has errors and the other device 
doesn't.  So it's not related to the drive bay it's related to the SSD.

The system is a Dell PowerEdge T630.

The SSD could have a fault, but if so why does it only show up on reboot and 
why 754 errors every time?

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/




             reply	other threads:[~2025-03-22 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 13:44 Russell Coker [this message]
2025-03-22 21:36 ` BTRFS error count 754 after reboot on Debian kernel 6.12.17 Qu Wenruo
2025-03-23  4:11   ` Russell Coker
2025-04-01  4:04 ` Chris Murphy
2025-04-01  5:18   ` Russell Coker
2025-04-01 16:00     ` Chris Murphy
2025-04-02  2:32       ` Russell Coker
2025-04-02  2:42         ` Chris Murphy
2025-04-02  5:01           ` Russell Coker

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=3349404.aeNJFYEL58@xev \
    --to=russell@coker.com.au \
    --cc=linux-btrfs@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