From: Dave Chinner <david@fromorbit.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
fstests@vger.kernel.org, btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas to do custom operation just after mount?
Date: Thu, 24 Dec 2015 10:17:03 +1100 [thread overview]
Message-ID: <20151223231703.GH26718@dastard> (raw)
In-Reply-To: <56778B9E.8050900@oracle.com>
On Mon, Dec 21, 2015 at 01:18:22PM +0800, Anand Jain wrote:
>
>
> >BTW, any good idea for btrfs to do such operation like
> >enabling/disabling some minor features? Especially when it can be set on
> >individual file/dirs.
> >
> >Features like incoming write time deduplication, is designed to be
> >enabled/disabled for individual file/dirs, so it's not a quite good idea
> >to use mount option to do it.
> >
> >Although some feature, like btrfs quota(qgroup), should be implemented
> >by mount option though.
> >I don't understand why qgroup is enabled/disabled by ioctl. :(
>
>
> mount option won't persist across systems/computers unless
> remembered by human.
So record the mount option you want persistent in the filesystem at
mount time and don't turn it off until a "no-...." mount option is
provided at mount time.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2015-12-23 23:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 1:55 Ideas to do custom operation just after mount? Qu Wenruo
2015-12-21 0:16 ` Dave Chinner
2015-12-21 2:25 ` Qu Wenruo
2015-12-21 2:38 ` Qu Wenruo
2015-12-21 5:18 ` Anand Jain
2015-12-22 0:14 ` Kai Krakow
2015-12-22 9:28 ` Duncan
2015-12-23 23:17 ` Dave Chinner [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=20151223231703.GH26718@dastard \
--to=david@fromorbit.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--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