From: Miao Xie <miaox@cn.fujitsu.com>
To: dsterba@suse.cz, Eric Sandeen <sandeen@redhat.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
Mark Fasheh <mfasheh@suse.de>
Subject: Re: [PATCH 2/2] Btrfs: introduce noextiref mount option
Date: Thu, 25 Apr 2013 19:27:01 +0800 [thread overview]
Message-ID: <51791305.50500@cn.fujitsu.com> (raw)
In-Reply-To: <20130415172050.GF18193@twin.jikos.cz>
On Mon, 15 Apr 2013 19:20:51 +0200, David Sterba wrote:
> On Fri, Apr 12, 2013 at 12:01:19PM -0500, Eric Sandeen wrote:
>> On 4/11/13 5:35 AM, Miao Xie wrote:
>>> Now, we set incompat flag EXTEND_IREF when we actually need insert a
>>> extend inode reference, not when making a fs. But some users may hope
>>> that the fs still can be mounted on the old kernel, and don't hope we
>>> insert any extend inode references. So we introduce noextiref mount
>>> option to close this function.
>>
>> I'd really rather not have yet another work-around mount option.
>>
>> Wouldn't it be better to say: if you don't want extended irefs, turn
>> that feature off on the filesystem itself, either at mkfs time or via
>> btrfstune after the fact.
>
> I agree with this, and hope the inconsistency around extref is only
> temporary so the mount options is not required in the long term.
>
> The code reverting extref set by default in mkfs is in integration
> branch.
>
> The preferred solution is the -O option where we can put all the fs
> features in one go at mkfs time.
All right, let's add a option for mkfs, and throw away this patchset.
Thanks.
Miao
prev parent reply other threads:[~2013-04-25 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 10:32 [PATCH 0/2] do not open the extend inode reference at the beginning Miao Xie
2013-04-11 10:33 ` [PATCH 1/2] Btrfs: set the INCOMPAT_EXTENDED_IREF when the extended iref is inserted Miao Xie
2013-04-11 10:35 ` [PATCH 2/2] Btrfs: introduce noextiref mount option Miao Xie
2013-04-11 14:29 ` Jan Schmidt
2013-04-12 4:13 ` Miao Xie
2013-04-12 7:02 ` Jan Schmidt
2013-04-15 2:58 ` Miao Xie
2013-04-15 5:25 ` Jan Schmidt
2013-04-15 5:36 ` Wang Shilong
2013-04-12 17:01 ` Eric Sandeen
2013-04-15 16:59 ` Mark Fasheh
2013-04-15 17:20 ` David Sterba
2013-04-25 11:27 ` Miao Xie [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=51791305.50500@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.