From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: Btrfs progs release 4.4
Date: Wed, 20 Jan 2016 19:04:30 +0100 [thread overview]
Message-ID: <20160120180430.GO4227@twin.jikos.cz> (raw)
In-Reply-To: <20160120091956.GN4227@suse.cz>
On Wed, Jan 20, 2016 at 10:19:56AM +0100, David Sterba wrote:
> On Wed, Jan 20, 2016 at 11:10:01AM +0800, Qu Wenruo wrote:
> > Not sure if it's intended or just a small miss, in btrfs-progs ctree.h,
> > there is BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE, but
> > BTRFS_FEATURE_COMPAT_RO_SUPP is still 0, not including FREE_SPACE_TREE.
> >
> > Is it intended as current btrfsck doesn't support to modify fs with new
> > free space cache tree?
>
> In progs it's unintended and buggy, the kernel side is buggy as well.
> I'm fixing it.
So it's just the btrfs-progs side, kernel side is fine.
prev parent reply other threads:[~2016-01-20 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 13:06 Btrfs progs release 4.4 David Sterba
2016-01-20 3:10 ` Qu Wenruo
2016-01-20 9:19 ` David Sterba
2016-01-20 18:04 ` 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=20160120180430.GO4227@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@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).