From: Nikolay Borisov <nborisov@suse.com>
To: x8062 <ericleaf@126.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: read time tree block corruption detected
Date: Tue, 23 Nov 2021 07:56:27 +0200 [thread overview]
Message-ID: <c5abf17e-85bc-c9ed-2c97-c323dc19f3f9@suse.com> (raw)
In-Reply-To: <46d6bc87.14b4.17d4aacd1dc.Coremail.ericleaf@126.com>
On 23.11.21 г. 4:42, x8062 wrote:
> At 2021-11-22 18:36:41, "Nikolay Borisov" <nborisov@suse.com> wrote:
>>
>>
>> On 22.11.21 г. 12:07, x8062 wrote:
>>> At 2021-11-22 15:24:38, "Nikolay Borisov" <nborisov@suse.com> wrote:
>>>>
>>>>
>>>> On 22.11.21 г. 7:26, x8062 wrote:
>>>>> 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
>>>>>
>>>>
>>>>
>>>> You have faulty ram, since 393 has the 17th bit set to 0 whilst has it
>>>> set to 1. So your ram is clearly corrupting bits. I advise you run a
>>>> memtest tool and look for possibly changing the faulty ram module.
>>>
>>> Thank you, can't believe the ram is not so stable. I'll run a memtest later.
>>
>> Actually according to the output this is a read-time corruption. THis
>> means the corrupted data has already been written to disk, likely by an
>> older kernel that didn't have the tree cherk code. So running a memcheck
>> is still useful to prevent future corruption.
>>
>> As far as the corrupted files goes - well its data is corrupted. It can
>> technically be fixed, but you'd have to do it yourself. Or alternatively
>> go back on an older kernel i.e pre- 5.11 and try to copy that particular
>> file (inode 2394634).
>>
>>>
> I find some problems here. I use the command "find . -inum 2394634" in the btrfs root dir, but nothing printed.
> does "root=381" means the subvolume ID=381? but now I don't have such subvolume. I deleted some of the
Yes root is the id of the subvolume, if you have deleted it then the
corrupted inode should also be gone.
> subvolumes a few days ago. this is the current subvolume list(some of the dir name shortened)
> sudo btrfs subvol list .
> ID 263 gen 111732 top level 5 path 8007/a
> ID 354 gen 111729 top level 5 path 8007/b
> ID 622 gen 111757 top level 5 path f015
> ID 1174 gen 111758 top level 5 path cc
> ID 1326 gen 111757 top level 5 path 8007/c
> ID 1781 gen 111740 top level 5 path ip
> ID 1782 gen 111758 top level 5 path og
> ID 1856 gen 111586 top level 1782 path og/OG/DB/server
> ID 1858 gen 111757 top level 622 path V6/db
> ID 1875 gen 111742 top level 5 path sdk
> ID 1918 gen 111742 top level 5 path 8015
> ID 1942 gen 111745 top level 5 path ip6
> ID 2007 gen 111758 top level 5 path mnew
> ID 2114 gen 111751 top level 5 path dd
> ID 2116 gen 111760 top level 2117 path ds/trunk/20200616
> ID 2117 gen 111758 top level 5 path ds
> ID 2118 gen 111758 top level 2114 path dd/trunk/sourcecode
> ID 2119 gen 111751 top level 2114 path dd/b/1103
> ID 2120 gen 111761 top level 5 path tt
>
next prev parent reply other threads:[~2021-11-23 5:56 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 5:26 read time tree block corruption detected x8062
2021-11-22 7:24 ` 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 [this message]
-- 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=c5abf17e-85bc-c9ed-2c97-c323dc19f3f9@suse.com \
--to=nborisov@suse.com \
--cc=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).