linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, Vegard Nossum <vegard.nossum@oracle.com>,
	Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
	David Sterba <dsterba@suse.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: BUG: failure at fs/btrfs/ctree.h:337/btrfs_chunk_item_size()!
Date: Fri, 4 Dec 2015 09:21:59 +0800	[thread overview]
Message-ID: <5660EAB7.1020702@cn.fujitsu.com> (raw)
In-Reply-To: <20151203174714.GD31035@suse.cz>



David Sterba wrote on 2015/12/03 18:47 +0100:
> On Tue, Dec 01, 2015 at 08:50:57AM +0800, Qu Wenruo wrote:
>> Btrfsck already gives quite good clue on the problem:
>>
>> ERROR: chunk_root block unaligned: 4294967168
>> ERROR: chunk_root block unaligned: 4294967168
>>
>> Chunk root in superblock is not aligned, and the superblock is not valid.
>>
>> It would be better to copy all these btrfs-progs enhancement to kernel.
>
> We do have the alignment check in kernel, but it's in the early phase
> where we don't know if nodesize is reliable and print only a warning.
>
>
This can be enhanced by the following method:

1) Check sectorsize first
    Only several sector size is valid for current btrfs:
    4K, 8K, 16K, 32K, 64K
    Just five numbers, quite easy to check.
    Or if anyone is going to extend supported sectorsize, we can change
    the check to if the number is power of 2 starting from 4K.

2) Check nodesize/leafsize then
    It should be aligned to sectorsize.
    And nodesize must match with leafsize.
    Currently, it's done out of check_super_valid(), we can integrate it.

3) Check all super root bytenr against *sectorsize*
    Yeah, not nodesize.
    As some old bad convert will cause metadata extent unaligned to
    nodesize(just before my convert rework patch), but only aligned to
    sectorsize.
    So only check alignment of sectorsize.

If you are OK with this idea, I can make the patch soon.

Thanks,
Qu





  reply	other threads:[~2015-12-04  1:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15 18:21 BUG: failure at fs/btrfs/ctree.h:337/btrfs_chunk_item_size()! Vegard Nossum
2015-11-30 13:48 ` David Sterba
2015-11-30 16:34   ` David Sterba
2015-11-30 22:05     ` Vegard Nossum
2015-12-01  0:50       ` Qu Wenruo
2015-12-03 17:47         ` David Sterba
2015-12-04  1:21           ` Qu Wenruo [this message]
2015-12-04 13:12             ` David Sterba
2015-12-05  6:52               ` Qu Wenruo
2015-12-03 17:59       ` David Sterba

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=5660EAB7.1020702@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=vegard.nossum@oracle.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).