From: Kai Krakow <hurikhan77@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Ideas to do custom operation just after mount?
Date: Tue, 22 Dec 2015 01:14:24 +0100 [thread overview]
Message-ID: <20151222011424.03247982@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 56778B9E.8050900@oracle.com
Am Mon, 21 Dec 2015 13:18:22 +0800
schrieb Anand Jain <anand.jain@oracle.com>:
>
>
> > 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.
Valid point, tho here's an counter-example: space-cache is persisted.
Once enabled, it's always there until you clear AND disable it during
initial mount.
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2015-12-22 3:00 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 [this message]
2015-12-22 9:28 ` Duncan
2015-12-23 23:17 ` Dave Chinner
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=20151222011424.03247982@jupiter.sol.kaishome.de \
--to=hurikhan77@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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