From: Samir Benmendil <me@rmz.io>
To: linux-btrfs@vger.kernel.org
Subject: Re: read time tree block corruption detected
Date: Sat, 15 Feb 2020 15:34:08 +0000 [thread overview]
Message-ID: <20200215153408.a3raoibms2nlxfn2@hactar> (raw)
In-Reply-To: <da987d5b-630f-bf41-8c5c-bb222d09e5a4@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]
On Feb 13, 2020 at 22:01, Qu Wenruo wrote:
> On 2020/2/13 上午8:26, Qu Wenruo wrote:
>> On 2020/2/13 上午5:58, Samir Benmendil wrote:
>>> I've been getting the following "BTRFS errors" for a while now, the
>>> wiki [0] advises to report such occurrences to this list.
>>
>> Please provide the following dump:
>>
>> # btrfs ins dump-tree -b 194756837376 /dev/sda2
>> # btrfs ins dump-tree -b 194347958272 /dev/sda2
>>>
>>> BTRFS critical (device sda2): corrupt leaf: root=466 block=194756837376
>>> slot=72 ino=1359622 file_offset=475136, extent end overflow, have file
>>> offset 475136 extent num bytes 18446744073709486080
>
> item 72 key (1359622 EXTENT_DATA 475136) itemoff 11140 itemsize 53
> generation 954719 type 1 (regular)
> extent data disk byte 0 nr 0
> extent data offset 0 nr 18446744073709486080 ram 18446744073709486080
> extent compression 0 (none)
>
> Also obvious underflow.
>
>>> BTRFS critical (device sda2): corrupt leaf: root=466 block=194347958272
>>> slot=131 ino=1357455 file_offset=1044480, extent end overflow, have file
>>> offset 1044480 extent num bytes 18446744073708908544
>
> item 131 key (1357455 EXTENT_DATA 1044480) itemoff 6497 itemsize 53
> generation 952602 type 1 (regular)
> extent data disk byte 0 nr 0
> extent data offset 0 nr 18446744073708908544 ram 18446744073708908544
> extent compression 0 (none)
>
> As you can see, 18446744073708908544 = -653072, which means it overflows.
>
> Both look like a bug in older kernels.
>
> Since currently btrfsprogs can't detect nor fix it yet, the only way is
> to delete the offending files.
>
> You can use the inode number 1357455, and root id 466 to locate the
> offending files, and delete it using older kernels.
> (root id is your subvolume id, which is shown in `btrfs subv list`.
> inode number can be passed to `find` command using `-inum` option)
I deleted the offending file for inode 1357455 using kernel 4.4.165.
However `find` did not return any results for inode 1359622. The newer
kernel doesn't seem to complain about that anymore though.
Thank you for you help Qu.
Regards
Samir
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-15 15:34 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 21:58 read time tree block corruption detected 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-22 5:26 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
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-01-16 13:40 read " 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=20200215153408.a3raoibms2nlxfn2@hactar \
--to=me@rmz.io \
--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).