From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Patrick Erley <pat-lkml@erley.org>, linux-btrfs@vger.kernel.org
Subject: Re: read time tree block corruption detected
Date: Mon, 30 Dec 2019 08:46:09 +0800 [thread overview]
Message-ID: <4bf17941-2ab0-15ca-b4c9-f6ba037624ee@gmx.com> (raw)
In-Reply-To: <CAOB=O_jxu5JOe=JiYVW_VZ1rgs9+mdHpAHkscXkc4MVRLrBKDw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2331 bytes --]
On 2019/12/30 上午4:43, Patrick Erley wrote:
> On a system where I've been tinkering with linux-next for years, my /
> has got some errors. When migrating from 5.1 to 5.2, I saw these
> errors, but just ignored them and went back to 5.1, and continued my
> tinkering. Over the holidays, I decided to try to upgrade the kernel,
> saw the errors again, and decided to look into them, finding the
> tree-checker page on the kernel docs, and am writing this e-mail.
>
> My / does not contain anything sensitive or important, as /home and
> /usr/src are both subvolumes on a separate larger drive.
>
> btrfs fi show:
> Label: none uuid: 815266d6-a8b9-4f63-a593-02fde178263f
> Total devices 2 FS bytes used 93.81GiB
> devid 1 size 115.12GiB used 115.11GiB path /dev/nvme0n1p2
> devid 3 size 115.12GiB used 115.11GiB path /dev/sda3
>
> Label: none uuid: 4bd97711-b63c-40cb-bfa5-aa9c2868cf98
> Total devices 1 FS bytes used 536.48GiB
> devid 1 size 834.63GiB used 833.59GiB path /dev/sda5
>
> Booting a more recent kernel, I get spammed with:
> [ 8.243899] BTRFS critical (device nvme0n1p2): corrupt leaf: root=5
> block=303629811712 slot=30 ino=5380870, invalid inode generation: has
> 13221446351398931016 expect [0, 2997884]
Inode generation repair is introduced in v5.4. So feel free to use
`btrfs check --repair` to repair such problems.
But please run a `btrfs check` without --repair and paste the output,
just in case there are extra problems which may screw up repair.
Thanks,
Qu
> [ 8.243902] BTRFS error (device nvme0n1p2): block=303629811712 read
> time tree block corruption detected
>
> There are 6 corrupted inodes:
> cat dmesg.foo | grep "BTRFS critical" | sed -re
> 's:.*block=([0-9]*).*ino=([0-9]+).*:\1 \2:' | sort | uniq
> 303629811712 5380870
> 303712501760 3277548
> 303861395456 5909140
> 304079065088 2228479
> 304573444096 3539224
> 305039556608 1442149
>
> and they all have the same value for the inode generation. Before I
> reboot into a livecd and btrfs check --repair, is there anything
> interesting that a snapshot of the state would show? I have 800gb
> unpartitioned on the nvme, so backing up before is already in the
> plans, and I could just as easily grab an image of the partitions
> while I'm at it.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2019-12-30 0:49 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 20:43 read time tree block corruption detected 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 [this message]
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
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
2020-02-12 21:58 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
[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
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
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-11-22 5:26 read " 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
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=4bf17941-2ab0-15ca-b4c9-f6ba037624ee@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pat-lkml@erley.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).