From: Larkin Lowrey <llowrey@nuclearwinter.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: Scrub aborts due to corrupt leaf
Date: Tue, 28 Aug 2018 09:29:14 -0400 [thread overview]
Message-ID: <0136878c-d4ae-37b0-4903-601367286cf7@nuclearwinter.com> (raw)
In-Reply-To: <273c99b2-d7e0-bea3-a4a4-7337115beb6f@nuclearwinter.com>
On 8/27/2018 10:12 PM, Larkin Lowrey wrote:
> On 8/27/2018 12:46 AM, Qu Wenruo wrote:
>>
>>> The system uses ECC memory and edac-util has not reported any errors.
>>> However, I will run a memtest anyway.
>> So it should not be the memory problem.
>>
>> BTW, what's the current generation of the fs?
>>
>> # btrfs inspect dump-super <device> | grep generation
>>
>> The corrupted leaf has generation 2862, I'm not sure how recent did the
>> corruption happen.
>
> generation 358392
> chunk_root_generation 357256
> cache_generation 358392
> uuid_tree_generation 358392
> dev_item.generation 0
>
> I don't recall the last time I ran a scrub but I doubt it has been
> more than a year.
>
> I am running 'btrfs check --init-csum-tree' now. Hopefully that clears
> everything up.
No such luck:
Creating a new CRC tree
Checking filesystem on /dev/Cached/Backups
UUID: acff5096-1128-4b24-a15e-4ba04261edc3
Reinitialize checksum tree
csum result is 0 for block 2412149436416
extent-tree.c:2764: alloc_tree_block: BUG_ON `ret` triggered, value -28
btrfs(+0x1da16)[0x55cc43796a16]
btrfs(btrfs_alloc_free_block+0x207)[0x55cc4379c177]
btrfs(+0x1602f)[0x55cc4378f02f]
btrfs(btrfs_search_slot+0xed2)[0x55cc43790be2]
btrfs(btrfs_csum_file_block+0x48f)[0x55cc437a213f]
btrfs(+0x55cef)[0x55cc437cecef]
btrfs(cmd_check+0xd49)[0x55cc437ddbc9]
btrfs(main+0x81)[0x55cc4378b4d1]
/lib64/libc.so.6(__libc_start_main+0xeb)[0x7f4717e6324b]
btrfs(_start+0x2a)[0x55cc4378b5ea]
Aborted (core dumped)
--Larkin
next prev parent reply other threads:[~2018-08-28 17:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 20:45 Scrub aborts due to corrupt leaf Larkin Lowrey
2018-08-27 0:16 ` Qu Wenruo
2018-08-27 2:32 ` Larkin Lowrey
2018-08-27 4:46 ` Qu Wenruo
2018-08-28 2:12 ` Larkin Lowrey
2018-08-28 3:29 ` Chris Murphy
2018-08-28 13:29 ` Larkin Lowrey [this message]
2018-08-28 13:42 ` Qu Wenruo
2018-08-28 13:56 ` Chris Murphy
2018-08-29 1:27 ` Qu Wenruo
2018-08-29 5:32 ` Qu Wenruo
2018-09-11 15:23 ` Larkin Lowrey
2018-10-10 15:44 ` Larkin Lowrey
2018-10-10 16:04 ` Holger Hoffstätte
2018-10-10 17:25 ` Larkin Lowrey
2018-10-10 18:20 ` Holger Hoffstätte
2018-10-10 18:31 ` Larkin Lowrey
2018-10-10 19:53 ` Chris Murphy
2018-10-10 23:43 ` Qu Wenruo
2018-10-10 17:44 ` Chris Murphy
2018-10-10 18:25 ` Holger Hoffstätte
2018-10-10 23:55 ` Hans van Kranenburg
2018-10-11 2:12 ` Larkin Lowrey
2018-10-11 2:51 ` Chris Murphy
2018-10-11 3:07 ` Larkin Lowrey
2018-10-11 4:00 ` Chris Murphy
2018-10-11 4:15 ` Chris Murphy
2018-12-31 15:52 ` Larkin Lowrey
2019-01-01 0:12 ` Qu Wenruo
2019-01-01 2:38 ` Larkin Lowrey
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=0136878c-d4ae-37b0-4903-601367286cf7@nuclearwinter.com \
--to=llowrey@nuclearwinter.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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).