From: Omar Sandoval <osandov@osandov.com>
To: Tobias Holst <tobby@tobby.eu>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: cannot mount read-write because of unsupported optional features (2)
Date: Tue, 1 Nov 2016 08:20:50 -0700 [thread overview]
Message-ID: <20161101152050.GA1707@vader> (raw)
In-Reply-To: <CAGwxe4hVacU31ZNQnw9tCPM8WZDdShmTSJwHi=fBA7hr3exQHw@mail.gmail.com>
On Tue, Nov 01, 2016 at 04:03:38PM +0100, Tobias Holst wrote:
> Ah thanks! Looks like I missed this bug on the list...
>
> But as I understand it, it should be mountable with btrfs-progs
> >=4.7.3 or when mounting it with "-o clear_cache,nospace_cache". But
> both doesn't work. Is it only mountable with kernel >=4.9 anymore?
> That would be interesting since I never ran a kernel newer than 4.8...
>
> Regards,
> Tobias
Hi, Tobias,
The fix was backported to v4.7 and v4.8 stable, so it's not just v4.9.
The btrfs-progs version doesn't matter for mounting. If you use a stable
kernel newer than v4.7.10 or v4.8.4, you will be able to mount it. If
you really need to use it with an older kernel, you can clear the free
space tree with -o clear_cache,nospace_cache from the newer kernel.
Sorry for the trouble, we really had to add this incompatability bit
even for x86 because of a btrfs-progs bug that could potentially corrupt
the free space tree.
--
Omar
prev parent reply other threads:[~2016-11-01 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 4:46 cannot mount read-write because of unsupported optional features (2) Tobias Holst
2016-11-01 5:24 ` Qu Wenruo
2016-11-01 15:03 ` Tobias Holst
2016-11-01 15:20 ` Omar Sandoval [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=20161101152050.GA1707@vader \
--to=osandov@osandov.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=tobby@tobby.eu \
/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).