public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Wengang Wang <wen.gang.wang@oracle.com>
To: Wengang Wang <wen.gang.wang@oracle.com>
Cc: greg.marsden@oracle.com, joe.jin@oracle.com, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: mkfs manpage -nsize/log
Date: Mon, 26 Apr 2010 20:32:10 +0800	[thread overview]
Message-ID: <20100426123210.GA3194@laptop.oracle.com> (raw)
In-Reply-To: <201004261155.o3QBFk83032745@rcsinet15.oracle.com>

Sorry.
Send description of this patch.

There are two limitation for mkfs.xfs -nsize/log option:
1) directory block size must be a power of 2 size.
2) it can't be less than a file system block size.

Current man page don't include the above information. User could
be confused with errors, say "Illegal value xxx for -n size option", but
they can't find out the cause by checking the man page.

The patch adds the two limitations to the manpage.

On 10-04-26 19:53, Wengang Wang wrote:
> Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
> ---
>  man/man8/mkfs.xfs.8 |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
> index 4b147e9..bdaa153 100644
> --- a/man/man8/mkfs.xfs.8
> +++ b/man/man8/mkfs.xfs.8
> @@ -478,6 +478,8 @@ in bytes with
>  or as a base two logarithm
>  .I value
>  .RB "with " log= .
> +The block size must be a power of 2 size and cannot be made less than the
> +filesystem block size.
>  The default size
>  .I value
>  for version 2 directories is 4096 bytes (4 KiB),
> -- 
> 1.6.6.1
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-04-26 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 11:53 [PATCH] xfsprogs: mkfs manpage -nsize/log Wengang Wang
2010-04-26 12:32 ` Wengang Wang [this message]
2010-04-26 15:59 ` Eric Sandeen

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=20100426123210.GA3194@laptop.oracle.com \
    --to=wen.gang.wang@oracle.com \
    --cc=greg.marsden@oracle.com \
    --cc=joe.jin@oracle.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