From: Martin Steigerwald <martin@lichtvoll.de>
To: dsterba@suse.cz, Nikolay Borisov <nborisov@suse.com>,
linux-btrfs@vger.kernel.org, Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: Criteria for mount messages. (was "Re: [PATCH] btrfs: remove skinny extent verbose message")
Date: Fri, 24 Jun 2022 12:52:19 +0200 [thread overview]
Message-ID: <1852203.CQOukoFCf9@ananda> (raw)
In-Reply-To: <7a42092f-9534-e54c-174e-8aaf17509d4b@gmx.com>
Qu Wenruo - 24.06.22, 00:46:02 CEST:
> Thus my idea criteria would be:
>
> - Would this feature bring bad impact to end users?
> If the feature is only bringing good impact, it should not be
> output.
>
> Thus in this way, v2 cache nowadays should also be skipped, as it's
> already well tested, and no real disadvantage at all.
There is one aspect where I find those messages helpful:
To confirm that I successfully enabled a feature (like space cache v2).
However, for that there does not really need to be a kernel message on
each mounting, as long as I have a way to confirm the currently used
features of BTRFS like:
- which checksum algorithm?
- space cache v2
- big metadata
- which compression method configured as standard (I am aware that does
not say anything about which files are compressed by which method)
and all other things like that.
Preferably in the output of just one command instead of being scattered
around several different outputs or not even available at all. For
example I am not aware of a command that confirms whether or not a
filesystem uses "xxhash" instead of "crc32c" as checksum algorithm.
Something a bit similar to "tune2fs -l" or "xfs_info".
Is there such a something? I believe there is some way to dump a
superblock however is there something that gives a structured output on
what features are in use on a given filesystem?
Best,
--
Martin
next prev parent reply other threads:[~2022-06-24 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 8:08 [PATCH] btrfs: remove skinny extent verbose message Nikolay Borisov
2022-06-23 8:22 ` Qu Wenruo
2022-06-23 8:30 ` Nikolay Borisov
2022-06-23 14:19 ` David Sterba
2022-06-23 22:46 ` Criteria for mount messages. (was "Re: [PATCH] btrfs: remove skinny extent verbose message") Qu Wenruo
2022-06-24 9:10 ` Forza
2022-06-24 10:52 ` Martin Steigerwald [this message]
2022-06-24 13:10 ` Forza
2022-06-23 9:30 ` [PATCH] btrfs: remove skinny extent verbose message Nikolay Borisov
2022-06-23 9:52 ` Qu Wenruo
2022-06-24 16:21 ` David Sterba
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=1852203.CQOukoFCf9@ananda \
--to=martin@lichtvoll.de \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=quwenruo.btrfs@gmx.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).