From: Jean-Christophe Guillain <jcguillain@sequans.com>
To: <tytso@mit.edu>
Cc: <darrick.wong@oracle.com>, <linux-ext4@vger.kernel.org>
Subject: Re: Metadata_csum is still enabled after trying to disable it.
Date: Mon, 26 Nov 2018 14:51:28 +0100 [thread overview]
Message-ID: <E1gRHIO-0002Z8-4e@eureka> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
----- On Nov 24, 2018, at 4:48 AM, Theodore Y. Ts'o tytso@mit.edu wrote:
> On Wed, Nov 21, 2018 at 07:01:19PM -0800, Darrick J. Wong wrote:
>> > Is it a bug ?
>>
>> Yes.
>>
>> > How can I actually disable this parameter ?
>>
>
> Actually, the metadata_csum feature *was* disabled. You would have
> seen that if you looked at the "Features: " line printed by dumpe2fs
> -h or tune2fs -l. The bug was that we were erroneously warning that
> the tune2fs -U operation would take a long time when flex_bg was
> enabled, but metadata_csum was not. So it was misleading wrong, but
> it actually turning off the metadata_csum feature.
>
Thank you very much for your time !
jC
[-- Attachment #2: Type: text/plain, Size: 335 bytes --]
-- IMPORTANT NOTICE:
The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next reply other threads:[~2018-11-27 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 13:51 Jean-Christophe Guillain [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-23 15:25 Metadata_csum is still enabled after trying to disable it Jean-Christophe Guillain
2018-11-21 17:48 Jean-Christophe Guillain
2018-11-22 3:01 ` Darrick J. Wong
2018-11-24 3:48 ` Theodore Y. Ts'o
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=E1gRHIO-0002Z8-4e@eureka \
--to=jcguillain@sequans.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).