From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Kai Krakow <hurikhan77@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck lowmem mode shows corruptions
Date: Fri, 5 May 2017 08:55:10 +0800 [thread overview]
Message-ID: <37157561-b48c-bde2-cf8f-c15e8fbf38d3@cn.fujitsu.com> (raw)
In-Reply-To: <20170504192936.5820aa76@jupiter.sol.kaishome.de>
At 05/05/2017 01:29 AM, Kai Krakow wrote:
> Hello!
>
> Since I saw a few kernel freezes lately (due to experimenting with
> ck-sources) including some filesystem-related backtraces, I booted my
> rescue system to check my btrfs filesystem.
>
> Luckily, it showed no problems. It said, everything's fine. But I also
> thought: Okay, let's try lowmem mode. And that showed a frightening
> long list of extent corruptions und unreferenced chunks. Should I worry?
Thanks for trying lowmem mode.
Would you please provide the version of btrfs-progs?
IIRC "ERROR: data extent[96316809216 2097152] backref lost" bug has been
fixed in recent release.
And for reference, would you please provide the tree dump of your chunk
and device tree?
This can be done by running:
# btrfs-debug-tree -t device <device>
# btrfs-debug-tree -t chunk <device>
And this 2 dump only contains the btrfs chunk mapping info, so nothing
sensitive is contained.
Thanks,
Qu
>
> PS: The freezes seem to be related to bfq, switching to deadline solved
> these.
>
> Full log attached, here's an excerpt:
>
> ---8<---
>
> checking extents
> ERROR: chunk[256 4324327424) stripe 0 did not find the related dev extent
> ERROR: chunk[256 4324327424) stripe 1 did not find the related dev extent
> ERROR: chunk[256 4324327424) stripe 2 did not find the related dev extent
> ERROR: chunk[256 7545552896) stripe 0 did not find the related dev extent
> ERROR: chunk[256 7545552896) stripe 1 did not find the related dev extent
> ERROR: chunk[256 7545552896) stripe 2 did not find the related dev extent
> [...]
> ERROR: device extent[1, 1094713344, 1073741824] did not find the related chunk
> ERROR: device extent[1, 2168455168, 1073741824] did not find the related chunk
> ERROR: device extent[1, 3242196992, 1073741824] did not find the related chunk
> [...]
> ERROR: device extent[2, 608854605824, 1073741824] did not find the related chunk
> ERROR: device extent[2, 609928347648, 1073741824] did not find the related chunk
> ERROR: device extent[2, 611002089472, 1073741824] did not find the related chunk
> [...]
> ERROR: device extent[3, 64433946624, 1073741824] did not find the related chunk
> ERROR: device extent[3, 65507688448, 1073741824] did not find the related chunk
> ERROR: device extent[3, 66581430272, 1073741824] did not find the related chunk
> [...]
> ERROR: data extent[96316809216 2097152] backref lost
> ERROR: data extent[96316809216 2097152] backref lost
> ERROR: data extent[96316809216 2097152] backref lost
> ERROR: data extent[686074396672 13737984] backref lost
> ERROR: data extent[686074396672 13737984] backref lost
> ERROR: data extent[686074396672 13737984] backref lost
> [...]
> ERROR: errors found in extent allocation tree or chunk allocation
> checking free space cache
> checking fs roots
> ERROR: errors found in fs roots
> Checking filesystem on /dev/disk/by-label/system
> UUID: bc201ce5-8f2b-4263-995a-6641e89d4c88
> found 1960075935744 bytes used, error(s) found
> total csum bytes: 1673537040
> total tree bytes: 4899094528
> total fs tree bytes: 2793914368
> total extent tree bytes: 190398464
> btree space waste bytes: 871743708
> file data blocks allocated: 6907169177600
> referenced 1979268648960
>
next prev parent reply other threads:[~2017-05-05 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 17:29 btrfsck lowmem mode shows corruptions Kai Krakow
2017-05-05 0:55 ` Qu Wenruo [this message]
2017-05-05 18:15 ` Kai Krakow
2017-05-10 3:09 ` Qu Wenruo
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=37157561-b48c-bde2-cf8f-c15e8fbf38d3@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=hurikhan77@gmail.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).