From: Yurii Kolesnykov <yurikoles@gmail.com>
To: Zhao Lei <zhaolei@cn.fujitsu.com>,
"'Chris Murphy'" <lists@colorremedies.com>,
"'Btrfs BTRFS'" <linux-btrfs@vger.kernel.org>
Cc: "'Qu Wenruo'" <quwenruo@cn.fujitsu.com>
Subject: Re: [BUG] kernel BUG at fs/btrfs/scrub.c:1956!, when scrubbing freshly converted ext4
Date: Wed, 26 Aug 2015 12:44:26 +0300 [thread overview]
Message-ID: <55DD8A7A.9030804@gmail.com> (raw)
In-Reply-To: <04eb01d0c4f9$80e42300$82ac6900$@cn.fujitsu.com>
Hi, Zhao Lei
>
> I reproduced above bug too, with following command:
> mkfs.ext4 /dev/vdh
> btrfs-convert /dev/vdh
> mount /dev/vdh /mnt/tmp1
> btrfs scrub start -B /dev/vdh
> (panic)
>
> The reason is:
> 1: In some case, metadata(leaf) created by btrfs-convert was split into 2 strips.
> 2: Then scrub bypassed part of leaf data, and left data caused panic in
> scrub_checksum_tree_block().
>
> For above 1:
> we can get following information after some simple operation.
> a. mkfs.ext4 /dev/vdh
> btrfs-convert /dev/vdh
> b. btrfs-debug-tree /dev/vdh
> we can see following item in extent tree:
> item 25 key (27054080 METADATA_ITEM 0) itemoff 15083 itemsize 33
> Its logical address is [27054080, 27070464)
> and acrossed 2 strips:
> [27000832, 27066368)
> [27066368, 27131904)
> Qu Wenruo <quwenruo@cn.fujitsu.com> is fixing above problem.
>
> For above 2:
> scrub is trying to do a "bypass" in this case, but the result is "panic".
> I'll fix it.
>
> Thanks
> Zhaolei
Could you please share an update on this bug status?
Also, please use bugzilla.
next prev parent reply other threads:[~2015-08-26 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 3:15 [BUG] kernel BUG at fs/btrfs/scrub.c:1956!, when scrubbing freshly converted ext4 Chris Murphy
2015-07-23 3:41 ` Zhao Lei
2015-08-26 9:44 ` Yurii Kolesnykov [this message]
2015-08-26 10:28 ` Zhao Lei
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=55DD8A7A.9030804@gmail.com \
--to=yurikoles@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo@cn.fujitsu.com \
--cc=zhaolei@cn.fujitsu.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).