From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: btrfs dev sta not updating
Date: Tue, 23 Jun 2020 12:09:36 +1000 [thread overview]
Message-ID: <4857863.FCrPRfMyHP@liv> (raw)
[395198.926320] BTRFS warning (device sdc1): csum failed root 5 ino 276 off
19267584 csum 0x8941f998 expected csum 0xccd545e0 mirror 1
[395199.147439] BTRFS warning (device sdc1): csum failed root 5 ino 276 off
20611072 csum 0x8941f998 expected csum 0xdaf657cb mirror 1
[395199.183680] BTRFS warning (device sdc1): csum failed root 5 ino 276 off
24190976 csum 0x8941f998 expected csum 0xcddce0b1 mirror 1
[395199.185172] BTRFS warning (device sdc1): csum failed root 5 ino 276 off
19267584 csum 0x8941f998 expected csum 0xccd545e0 mirror 1
[395199.330841] BTRFS warning (device sdc1): csum failed root 5 ino 277 off 0
csum 0x8941f998 expected csum 0xa54d865c mirror 1
I have a USB stick that's corrupted, I get the above kernel messages when I
try to copy files from it. But according to btrfs dev sta it has had 0 read
and 0 corruption errors.
root@xev:/mnt/tmp# btrfs dev sta .
[/dev/sdc1].write_io_errs 0
[/dev/sdc1].read_io_errs 0
[/dev/sdc1].flush_io_errs 0
[/dev/sdc1].corruption_errs 0
[/dev/sdc1].generation_errs 0
root@xev:/mnt/tmp# uname -a
Linux xev 5.6.0-2-amd64 #1 SMP Debian 5.6.14-1 (2020-05-23) x86_64 GNU/Linux
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2020-06-23 2:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 2:09 Russell Coker [this message]
2020-06-23 6:03 ` btrfs dev sta not updating Nikolay Borisov
2020-06-23 6:17 ` waxhead
2020-06-23 7:11 ` Nikolay Borisov
2020-06-23 8:00 ` Russell Coker
2020-06-23 8:17 ` Nikolay Borisov
2020-06-23 9:48 ` Russell Coker
2020-06-23 11:13 ` Nikolay Borisov
2020-06-23 11:21 ` Russell Coker
2020-06-24 11:39 ` Zygo Blaxell
2020-06-24 13:04 ` Nikolay Borisov
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=4857863.FCrPRfMyHP@liv \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.