From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: uninit_bg removed from mke2fs.conf
Date: Sat, 29 Sep 2018 11:19:09 -0400 [thread overview]
Message-ID: <20180929151908.GB2290@thunk.org> (raw)
In-Reply-To: <ac3c94bd-adf7-eb8a-f776-e6f3a31f9df9@gmail.com>
On Sat, Sep 29, 2018 at 03:39:06PM +0200, Xose Vazquez Perez wrote:
>
> It was removed from misc/mke2fs.conf.in in d0b9e0a6aa7d6805338a43b4e372623352d8df09
>
> Was it intentional?
Yes, metadata_csum's functionality is a superset of uninit_bg with a
different way of checksuming the block group descriptors. So it's
contradictory to have both metadata_csum and uninit_bg enabled at the
same time.
- Ted
prev parent reply other threads:[~2018-09-29 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 13:39 uninit_bg removed from mke2fs.conf Xose Vazquez Perez
2018-09-29 15:19 ` Theodore Y. Ts'o [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=20180929151908.GB2290@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=xose.vazquez@gmail.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).