From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Tsutomu Itoh <t-itoh@jp.fujitsu.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: doc: fix incorrect format of 'l' option in mkfs.btrfs
Date: Thu, 25 Dec 2014 10:02:27 +0900 [thread overview]
Message-ID: <549B6223.6080205@jp.fujitsu.com> (raw)
In-Reply-To: <201412240710.AA00005@WIN-R1VKH1IH438.jp.fujitsu.com>
Hi Tsutomu,
On 2014/12/24 16:10, Tsutomu Itoh wrote:
> The format of 'l' option in mkfs.btrfs.txt is wrong.
> And, when the head of the character string is 65536, the following warning
> is displayed.
>
> $ make
> Making all in Documentation
> [ASCII] mkfs.btrfs.xml
> asciidoc: WARNING: mkfs.btrfs.xml.tmp1: line 67: list item index: expected 1 got 65536
> [XMLTO] mkfs.btrfs.8
> [GZ] mkfs.btrfs.8.gz
> rm mkfs.btrfs.8 mkfs.btrfs.xml
>
> So, fix it.
>
> Signed-off-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
It looks good to me.
Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Current man 8 mkfs.btrfs is wrong as follows.
===============================================================================
...
-n|--nodesize <size>
+ -l|--leafsize <size>:: Specify the nodesize, the tree block size in which btrfs stores data. The default value
is 16KB (16384) or the page size, whichever is bigger. Must be a multiple of the sectorsize, but not larger than
65536. Leafsize always equals nodesize and the options are aliases.
...
===============================================================================
In addition, after removing '+' between '-n' and '-l'
to fix this problem, the warning which you said is displayed.
After applying this patch, both two problems disappeared.
Thanks,
Satoru
> ---
> Documentation/mkfs.btrfs.txt | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/mkfs.btrfs.txt b/Documentation/mkfs.btrfs.txt
> index ba7e42b..01b615d 100644
> --- a/Documentation/mkfs.btrfs.txt
> +++ b/Documentation/mkfs.btrfs.txt
> @@ -59,19 +59,18 @@ By default, mkfs.btrfs will not write to the device if it suspects that
> there is a filesystem or partition table on the device already.
>
> -n|--nodesize <size>
> -+
> +
> -l|--leafsize <size>::
> Specify the nodesize, the tree block size in which btrfs stores
> data. The default value is 16KB (16384) or the page size, whichever is
> -bigger. Must be a multiple of the sectorsize, but not larger than
> -65536. Leafsize always equals nodesize and the options are aliases.
> +bigger. Must be a multiple of the sectorsize, but not larger than 65536.
> +Leafsize always equals nodesize and the options are aliases.
>
> -L|--label <name>::
> Specify a label for the filesystem.
> +
> NOTE: <name> should be less than 256 characters.
>
> -
> -m|--metadata <profile>::
> Specify how metadata must be spanned across the devices specified. Valid
> values are 'raid0', 'raid1', 'raid5', 'raid6', 'raid10', 'single' or 'dup'.
>
prev parent reply other threads:[~2014-12-25 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 7:10 [PATCH] btrfs-progs: doc: fix incorrect format of 'l' option in mkfs.btrfs Tsutomu Itoh
2014-12-25 1:02 ` Satoru Takeuchi [this message]
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=549B6223.6080205@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.