public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: cem@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH V2] mkfs: Improve warning when AG size is a multiple of stripe width
Date: Mon, 18 Sep 2023 08:52:49 +1000	[thread overview]
Message-ID: <ZQeDQW7a7eBt3vGp@dread.disaster.area> (raw)
In-Reply-To: <20230915102246.108709-1-cem@kernel.org>

On Fri, Sep 15, 2023 at 12:22:46PM +0200, cem@kernel.org wrote:
> 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>

I'm fine with this but, as I said in my previous comment, a man page
update for agsize is also needed. Something like this:

	agsize=value
		This is an alternative to using the agcount
		suboption. The value is the desired size of the
-		allocation group expressed in bytes (usually using
-		the m or g suffixes).  This value must be a multiple
-		of the filesystem block size, and must be at  least
+		allocation group expressed as a multiple of the
+		filesystem block size.  It must be at  least
		16MiB, and no more than 1TiB, and may be
		automatically adjusted to properly align with the
		stripe geometry.  The agcount and agsize suboptions
		are mutually exclusive.

-Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2023-09-17 22:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 10:22 [PATCH V2] mkfs: Improve warning when AG size is a multiple of stripe width cem
2023-09-15 15:03 ` Bill O'Donnell
2023-09-17 22:52 ` Dave Chinner [this message]
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=ZQeDQW7a7eBt3vGp@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=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