From: Christoph Hellwig <hch@infradead.org>
To: Wengang Wang <wen.gang.wang@oracle.com>
Cc: greg.marsden@oracle.com, joe.jin@oracle.com, xfs@oss.sgi.com
Subject: Re: mkfs.xfs man page for -nsize
Date: Thu, 22 Apr 2010 12:33:55 -0400 [thread overview]
Message-ID: <20100422163355.GA6360@infradead.org> (raw)
In-Reply-To: <20100422124118.GA3406@laptop.oracle.com>
On Thu, Apr 22, 2010 at 08:41:18PM +0800, Wengang Wang wrote:
> I got no idea why the value is illegal.
>
> Checking the codes, I found it also must be larger or equal to block size and it
> must be in powers of 2, 2^N. Should we add these two limitation to man page?
Yes, this should be added to the man page. Can you submit a patch to
add it?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-22 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 12:41 mkfs.xfs man page for -nsize Wengang Wang
2010-04-22 16:33 ` Christoph Hellwig [this message]
2010-04-23 1:56 ` Wengang Wang
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=20100422163355.GA6360@infradead.org \
--to=hch@infradead.org \
--cc=greg.marsden@oracle.com \
--cc=joe.jin@oracle.com \
--cc=wen.gang.wang@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