From: Eric Sandeen <sandeen@sandeen.net>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs: add missing noalign suboption information
Date: Mon, 08 Jul 2013 19:01:37 -0500 [thread overview]
Message-ID: <51DB52E1.8030508@sandeen.net> (raw)
In-Reply-To: <1373327110-5533-1-git-send-email-cmaiolino@redhat.com>
On 7/8/13 6:45 PM, Carlos Maiolino wrote:
> Adds to the mkfs man page, information about noalign mkfs option which is
> missing until now.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> man/man8/mkfs.xfs.8 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
> index 04c19b4..2435814 100644
> --- a/man/man8/mkfs.xfs.8
> +++ b/man/man8/mkfs.xfs.8
> @@ -244,6 +244,12 @@ will automatically query the logical volume for appropriate
> and
> .B swidth
> values.
> +.TP
> +.BI noalign
> +This option is used to bypass data alignment configuration. In rare
> +circunstances, data alignment might decrease performance, for such cases,
> +use this option to avoid data alignment, this will set stripe unit and
> +stripe width to 0.
Thanks for this, Carlos.
I think it might be better to just state plainly that it overrides automatic
stripe unit detection, and leave the tuning / performance parts out.
Most of the manpage today is more "what" than "why."
So maybe simply:
+This option disables automatic stripe geometry detection, and creates
+the filesystem without stripe geometry even if the underlying storage
+device reports this information.
FWIW, there is a 'noalign' option for the realtime subvolume
as well, and that should probably get documented too.
-Eric
> .RE
> .TP
> .B \-f
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-09 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 23:45 [PATCH] mkfs: add missing noalign suboption information Carlos Maiolino
2013-07-09 0:01 ` Eric Sandeen [this message]
2013-07-10 13:29 ` 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=51DB52E1.8030508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=cmaiolino@redhat.com \
--cc=xfs@oss.sgi.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