From: x8062 <ericleaf@126.com>
To: linux-btrfs@vger.kernel.org
Subject: read time tree block corruption detected
Date: Mon, 22 Nov 2021 13:26:04 +0800 (CST) [thread overview]
Message-ID: <56d93523.27d4.17d461bc3c6.Coremail.ericleaf@126.com> (raw)
Hello,
I got periodic warns in my linux console. in dmesg it is the following pasted text.
At https://btrfs.wiki.kernel.org/index.php/Tree-checker I learned it may be a error, so i send the message. Hopefully it could help, Thanks in advance!
[ 513.900852] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 513.900869] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 513.901534] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 513.901550] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 513.912414] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 513.912433] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 611.835932] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 611.835950] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 611.836594] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 611.836603] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 611.847484] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 611.847500] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 708.354174] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 708.354186] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 708.354833] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 708.354841] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
[ 708.357409] BTRFS critical (device sdb3): corrupt leaf: root=381 block=71928348672 slot=74 ino=2394634 file_offset=0, invalid ram_bytes for uncompressed inline extent, have 393 expect 131465
[ 708.357420] BTRFS error (device sdb3): block=71928348672 read time tree block corruption detected
BTW: my mount option is (rw,relatime,space_cache,commit=90,subvolid=5,subvol=/), I'm using btrfs upon /dev/sdb3 and /dev/sda4, with btrfs raid0 support.
$ uname -a
Linux XXXP 5.15.3-arch1-1 #1 SMP PREEMPT Thu, 18 Nov 2021 22:23:08 +0000 x86_64 GNU/Linux
$ pacman -Qi btrfs-progs
Name : btrfs-progs
Version : 5.15-1
Description : Btrfs filesystem utilities
Architecture : x86_64
URL : https://btrfs.wiki.kernel.org
Licenses : GPL2
Groups : None
Provides : btrfs-progs-unstable
Depends On : glibc util-linux-libs lzo zlib zstd libgcrypt
Optional Deps : python: libbtrfsutil python bindings [installed]
e2fsprogs: btrfs-convert [installed]
reiserfsprogs: btrfs-convert [installed]
Required By : None
Optional For : None
Conflicts With : btrfs-progs-unstable
Replaces : btrfs-progs-unstable
Installed Size : 4.80 MiB
Packager : Tobias Powalowski <tpowa@archlinux.org>
Build Date : Sun 07 Nov 2021 02:56:20 AM CST
Install Date : Tue 09 Nov 2021 01:10:11 PM CST
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
next reply other threads:[~2021-11-22 5:59 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 5:26 x8062 [this message]
2021-11-22 7:24 ` read time tree block corruption detected Nikolay Borisov
2021-11-22 10:07 ` x8062
2021-11-22 10:36 ` Nikolay Borisov
2021-11-23 2:42 ` x8062
2021-11-23 5:56 ` Nikolay Borisov
-- strict thread matches above, loose matches on Subject: below --
2021-07-17 1:45 Read " pepperpoint
2021-07-17 7:05 ` Qu Wenruo
[not found] ` <162650555086.7.16811903270475408953.10183708@simplelogin.co>
2021-07-17 7:51 ` pepperpoint
[not found] ` <162650826457.7.1050455337652772013.10184548@mb.ardentcoding.com>
2021-07-17 8:14 ` Qu Wenruo
[not found] ` <162650966150.7.11743767259405124657.10185986@simplelogin.co>
2021-07-17 8:57 ` pepperpoint
2021-07-17 10:12 ` Qu Wenruo
[not found] ` <162651674065.6.7912816287233908759.10188327@simplelogin.co>
2021-07-17 10:34 ` pepperpoint
[not found] ` <162651809235.7.7061042874033963922.10188873@mb.ardentcoding.com>
2021-07-17 10:48 ` Qu Wenruo
[not found] ` <162651892663.6.17938009695497100557.10189169@simplelogin.co>
2021-07-17 12:51 ` pepperpoint
[not found] ` <CQeY09U34m7SrT6nTAlkSQrbLJtmyKF1tDfuGDtKUkwJqujMI_nZU4MpGiU4F_Q1U3Lk1aWD1mFCT5SlsOsOcILWECflIw7EhVQTQpy_1Ts=@email.ardentcoding.com>
2021-07-18 5:26 ` pepperpoint
2021-07-18 7:15 ` Qu Wenruo
[not found] ` <162659327011.8.12718249358254503695.10218325@simplelogin.co>
2021-07-18 8:46 ` pepperpoint
[not found] ` <162659797656.6.14385932343235367381.10220447@mb.ardentcoding.com>
2021-07-18 9:32 ` Qu Wenruo
[not found] ` <162660074747.7.3300740266059717894.10221270@simplelogin.co>
2021-07-18 10:34 ` pepperpoint
[not found] ` <162660447733.8.9782212603273165785.10222524@mb.ardentcoding.com>
2021-07-18 11:13 ` Qu Wenruo
[not found] ` <162660684635.8.12423097770824212671.10223516@simplelogin.co>
2021-07-18 12:16 ` pepperpoint
2021-04-16 19:35 read " Gervais, Francois
2021-04-17 1:01 ` Qu Wenruo
2021-04-19 13:20 ` Gervais, Francois
2021-04-19 13:33 ` Qu Wenruo
2021-04-19 14:56 ` Gervais, Francois
2021-04-20 1:34 ` Qu Wenruo
2021-04-20 14:19 ` Gervais, Francois
2021-04-20 23:47 ` Qu Wenruo
2021-04-21 14:17 ` Gervais, Francois
2021-04-21 23:01 ` Qu Wenruo
2021-04-22 14:26 ` Gervais, Francois
2021-05-26 23:03 ` Gervais, Francois
2021-05-26 23:25 ` Qu Wenruo
[not found] <CAJheHN0FUe-ijMco1ZOc6iKF2zbPocOw+iiVNeTT1r-JuXOJww@mail.gmail.com>
2020-05-06 21:54 ` Fwd: Read " Tyler Richmond
2020-05-06 23:55 ` Chris Murphy
2020-05-07 0:51 ` Tyler Richmond
2020-05-07 1:06 ` Chris Murphy
2020-02-12 21:58 read " Samir Benmendil
2020-02-13 0:26 ` Qu Wenruo
2020-02-13 13:04 ` Samir Benmendil
2020-02-13 14:01 ` Qu Wenruo
2020-02-15 15:34 ` Samir Benmendil
2020-01-16 13:40 Peter Luladjiev
2020-01-16 16:12 ` Nikolay Borisov
[not found] ` <CA+ZCqs5=N5Hdf3NxZAmPCnA8wbcJPrcH8zM-fRbt-w8tL+TjUQ@mail.gmail.com>
2020-01-17 7:34 ` Nikolay Borisov
2020-01-17 7:51 ` Peter Luladjiev
2020-01-17 7:54 ` Peter Luladjiev
2020-01-17 7:59 ` Qu Wenruo
2020-01-17 8:14 ` Nikolay Borisov
2020-01-17 8:22 ` Peter Luladjiev
2020-01-17 9:10 ` Nikolay Borisov
2020-01-17 12:04 ` Peter Luladjiev
2019-12-29 20:43 Patrick Erley
2019-12-29 22:07 ` Chris Murphy
2019-12-29 22:27 ` Patrick Erley
2019-12-29 22:32 ` Chris Murphy
2019-12-29 22:36 ` Patrick Erley
2019-12-29 23:11 ` Chris Murphy
2019-12-29 23:19 ` Patrick Erley
2019-12-29 23:24 ` Chris Murphy
2019-12-29 23:26 ` Patrick Erley
2019-12-30 0:46 ` Qu Wenruo
2019-12-30 5:36 ` Patrick Erley
2019-12-30 5:43 ` Qu Wenruo
2019-12-30 5:47 ` Patrick Erley
2019-12-30 5:50 ` Patrick Erley
2019-12-30 5:58 ` Qu Wenruo
2019-12-30 6:07 ` Patrick Erley
2019-12-30 6:09 ` Qu Wenruo
2019-12-30 8:14 ` Patrick Erley
2019-12-30 8:54 ` Qu Wenruo
2019-12-30 9:01 ` Patrick Erley
2019-12-30 9:09 ` Qu Wenruo
2019-12-30 9:21 ` Patrick Erley
2019-12-30 9:27 ` Qu Wenruo
2019-12-30 10:06 ` Patrick Erley
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=56d93523.27d4.17d461bc3c6.Coremail.ericleaf@126.com \
--to=ericleaf@126.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).