From: Russell Coker <russell@coker.com.au>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Chris Murphy <lists@colorremedies.com>
Subject: Re: BTRFS error count 754 after reboot on Debian kernel 6.12.17
Date: Tue, 01 Apr 2025 16:18:15 +1100 [thread overview]
Message-ID: <3682098.taCxCBeP46@cupcakke> (raw)
In-Reply-To: <834224db-bd52-41ee-bce4-599cf12183c2@app.fastmail.com>
On Tuesday, 1 April 2025 15:04:20 AEDT Chris Murphy wrote:
> These are likely old errors. You'd need to check old logs to see when the
> write errors occurred. These statistics are just a counter. You can reset
> them with `btrfs dev stats -z` and they'll go back to zero.
>
> It's simple counter. It could be 754 errors seen one time. Or it could be `1
> error seen 754 times. Or any combination of multiple errors multiple times
> adding up to 754 errors.
Is "btrfs dev stats -z" covered by removing the device from the set and adding
it again? If so I did that but it kept recurring. The fact that the error
count was there in the first place wasn't the unexpected thing, it was the
fact that it kept coming back and had no log entries about it.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2025-04-01 5:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 13:44 BTRFS error count 754 after reboot on Debian kernel 6.12.17 Russell Coker
2025-03-22 21:36 ` Qu Wenruo
2025-03-23 4:11 ` Russell Coker
2025-04-01 4:04 ` Chris Murphy
2025-04-01 5:18 ` Russell Coker [this message]
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=3682098.taCxCBeP46@cupcakke \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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