From: Dave Chinner <david@fromorbit.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: sandeen@sandeen.net, linux-xfs@vger.kernel.org
Subject: Re: [RFC v2] mkfs.xfs: add mkfs.xfs.conf parse support using libini_config
Date: Sat, 3 Mar 2018 09:04:59 +1100 [thread overview]
Message-ID: <20180302220459.GU30854@dastard> (raw)
In-Reply-To: <20180302203228.9622-1-mcgrof@kernel.org>
On Fri, Mar 02, 2018 at 12:32:28PM -0800, Luis R. Rodriguez wrote:
> You may want to stick to specific set of configuration options when
> creating filesystems with mkfs.xfs -- sometimes due to pure technical
> reasons, but some other times to ensure systems remain compatible as
> new features are introduced with older kernels, or if you always want
> to take advantage of some new feature which would otherwise typically
> be disruptive.
>
> Although mkfs.xfs already uses sensible defaults this adds a configuration
> option for parsing defaults settings for mkfs.xfs parsed prior to processing
> input arguments from the command line.
>
> We define an XFS configuration directory, /etc/mkfs.xfs.d/ and allow for
> different types of configuration files, if none is specified we look for
> the default type, /etc/mkfs.xfs.d/default, and you can override with -t.
> For instance if you specify:
>
> mkfs.xfs -t experimental -f /dev/loop0
I haven't looked at the code at all, but I'll just make this initial
comment now: please don't use "-t" with mkfs.xfs.
"-t <type>" is a reserved flag used by the mkfs multiplexor to
specify the filesystem type, and so cannot be passed to filesystem
specific mkfs binaries. Hence we should not be using it in the
mkfs.xfs binary.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-03-02 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 20:32 [RFC v2] mkfs.xfs: add mkfs.xfs.conf parse support using libini_config Luis R. Rodriguez
2018-03-02 22:04 ` Dave Chinner [this message]
2018-03-03 5:01 ` Eric Sandeen
2018-03-03 17:45 ` Darrick J. Wong
2018-03-03 22:53 ` 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=20180302220459.GU30854@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sandeen@sandeen.net \
/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).