From: cem@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [PATCH V2] mkfs: Improve warning when AG size is a multiple of stripe width
Date: Fri, 15 Sep 2023 12:22:46 +0200 [thread overview]
Message-ID: <20230915102246.108709-1-cem@kernel.org> (raw)
From: Carlos Maiolino <cmaiolino@redhat.com>
The current output message prints out a suggestion of an AG size to be
used in lieu of the user-defined one.
The problem is this suggestion is printed in filesystem blocks, without
specifying the suffix to be used.
This patch tries to make user's life easier by outputing the option as
it should be used by the mkfs, so users can just copy/paste it.
Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
---
V2:
- Keep printing it in FSBs, just add the agsize= and the 'b' suffix at
the end
mkfs/xfs_mkfs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
index d3a15cf44..b61934e57 100644
--- a/mkfs/xfs_mkfs.c
+++ b/mkfs/xfs_mkfs.c
@@ -3179,9 +3179,9 @@ _("agsize rounded to %lld, sunit = %d\n"),
if (cli_opt_set(&dopts, D_AGCOUNT) ||
cli_opt_set(&dopts, D_AGSIZE)) {
printf(_(
-"Warning: AG size is a multiple of stripe width. This can cause performance\n\
-problems by aligning all AGs on the same disk. To avoid this, run mkfs with\n\
-an AG size that is one stripe unit smaller or larger, for example %llu.\n"),
+"Warning: AG size is a multiple of stripe width. This can cause performance\n\
+problems by aligning all AGs on the same disk. To avoid this, run mkfs with\n\
+an AG size that is one stripe unit smaller or larger, for example: agsize=%llub\n"),
(unsigned long long)cfg->agsize - dsunit);
fflush(stdout);
goto validate;
--
2.39.2
next reply other threads:[~2023-09-15 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 10:22 cem [this message]
2023-09-15 15:03 ` [PATCH V2] mkfs: Improve warning when AG size is a multiple of stripe width Bill O'Donnell
2023-09-17 22:52 ` Dave Chinner
2023-09-18 7:45 ` Carlos Maiolino
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=20230915102246.108709-1-cem@kernel.org \
--to=cem@kernel.org \
--cc=linux-xfs@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