From: David Sterba <dsterba@suse.cz>
To: Shilong Wang <wangshilong1991@gmail.com>
Cc: Philipp Matthias Hahn <pmhahn@pmhahn.de>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [BUG] open_ctree() failes after mounting BTRFS with 3.2 after 3.12
Date: Mon, 16 Dec 2013 14:46:35 +0100 [thread overview]
Message-ID: <20131216134635.GC6498@twin.jikos.cz> (raw)
In-Reply-To: <CAP9B-Q=0wWxXH5usnOq6MGN-LQZfw5y8dxgLZYidu_oPsOxrjQ@mail.gmail.com>
On Sun, Dec 15, 2013 at 10:03:35PM +0800, Shilong Wang wrote:
> I compile btrfs in kernel 3.2 and 3.12.
>
> # mkfs.btrfs -f /dev/sda2
> # mount /dev/sda2 /mnt
> # dd if=/dev/zero of=/mnt/data bs=1M count=1024
> # umount /mnt
>
> The above operations is in 3.2
>
> and then i switch my system into 3.12, and try to mount /dev/sda2
> it will output something like the following:
>
> btrfs: mismatching generation and generation_v2 found in root item.
> This root was probably mounted with an older kernel. Resetting all new
> fields.
>
> But it mounted successfully, then i do some similar operations in
> 3.12...and umount it.
> and switch into kernel version 3.2...
>
> but i failt to mount it in 3.2 and it output the following message.
>
> BTRFS: couldn't mount because of unsupported optional features (20)
BTRFS_FEATURE_INCOMPAT_BIG_METADATA (1ULL << 5)
== 0x20
so you've made the filesystem with new progs that turn on bigblocks by
default.
> It seems that here the problem is because incompat features in newer
> kernel and make older kernel
> unmountable any more..
This is not the case for any incompat feature introduced after 3.2.
Default subolume, lzo compression are automatically set when the feature
is used, but nothing from the rest like bigblocks, extrefs, skinny
metadata etc.
prev parent reply other threads:[~2013-12-16 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 9:58 [BUG] open_ctree() failes after mounting BTRFS with 3.2 after 3.12 Philipp Matthias Hahn
2013-12-15 14:03 ` Shilong Wang
2013-12-16 13:46 ` David Sterba [this message]
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=20131216134635.GC6498@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=pmhahn@pmhahn.de \
--cc=wangshilong1991@gmail.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).