From: "Scott E. Blomquist" <sb@techsquare.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: checksum error...
Date: Mon, 8 Apr 2019 11:48:03 -0400 [thread overview]
Message-ID: <23723.27955.359573.44839@techsquare.com> (raw)
Hi All,
The weekend btrfs scrub/balance came back with this following...
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271471, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 62378, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 270894, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271453, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271449, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271435, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271432, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271421, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271411, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271401, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271391, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271345, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271253, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271163, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 271074, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS warning (device sdb1): checksum error at logical 274820497408 on dev /dev/sda1, sector 536758784, root 270983, inode 109421914, offset 491520, length 4096, links 1 (path: yyyy/yyyyy)
[Sun Apr 7 06:57:10 2019] BTRFS error (device sdb1): bdev /dev/sda1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0
[Sun Apr 7 06:57:10 2019] BTRFS error (device sdb1): unable to fixup (regular) error at logical 274820497408 on dev /dev/sda1
Here is what I have...
root@cbmm-fsb:~# uname -a
Linux cbmm-fsb 4.14.24-custom #1 SMP Mon Mar 5 10:10:39 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
root@cbmm-fsb:~# btrfs --version
btrfs-progs v4.15.1
root@cbmm-fsb:~# btrfs fi show
Label: none uuid: d83b1e28-db27-4035-8638-d4b2eb824ff2
Total devices 2 FS bytes used 80.09TiB
devid 1 size 76.40TiB used 62.49TiB path /dev/sda1
devid 2 size 32.74TiB used 18.83TiB path /dev/sdb1
root@cbmm-fsb:~# btrfs fi df /home/cbcl
Data, single: total=79.80TiB, used=79.80TiB
System, RAID1: total=32.00MiB, used=9.09MiB
Metadata, RAID1: total=757.00GiB, used=281.34GiB
Metadata, DUP: total=22.50GiB, used=19.27GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
sda and sdb are megaraid raid6 with BBU and both are optimal.
Any tips? Thanks.
sb. Scott Blomquist
next reply other threads:[~2019-04-08 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 15:48 Scott E. Blomquist [this message]
2019-04-08 16:29 ` checksum error Hugo Mills
2019-04-08 18:40 ` Scott E. Blomquist
2019-04-15 13:14 ` Patrik Lundquist
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=23723.27955.359573.44839@techsquare.com \
--to=sb@techsquare.com \
--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;
as well as URLs for NNTP newsgroup(s).