From: Alvin Zheng <Alvin@linux.alibaba.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
"darrick.wong" <darrick.wong@oracle.com>,
caspar <caspar@linux.alibaba.com>
Subject: Re: [PATCH xfsprogs manual] Inconsistency between the code and the manual page
Date: Thu, 13 Jun 2019 18:23:18 +0800 [thread overview]
Message-ID: <39ccf3a5-a191-847a-1d68-67e040edc4ed@linux.alibaba.com> (raw)
In-Reply-To: <20190612221957.GF14363@dread.disaster.area>
On 2019/6/13 6:19, Dave Chinner wrote:
> On Wed, Jun 12, 2019 at 01:20:46PM +0800, Alvin Zheng wrote:
>> Hi,
>>
>> The manual page of mkfs.xfs (xfsprogs-5.0.0) says "When specifying
>> parameters in units of sectors or filesystem blocks, the -s option or the -b
>> option first needs to be added to the command line. Failure to specify the
>> size of the units will result in illegal value errors when parameters are
>> quantified in those units". However, I read the code and found that if the
>> size of the block and sector is not specified, the default size (block: 4k,
>> sector: 512B) will be used. Therefore, the following commands can work
>> normally in xfsprogs-5.0.0.
>>
>> mkfs.xfs -n size=2b /dev/vdc
>> mkfs.xfs -d agsize=8192b /dev/vdc
>>
>> So I think the manual of mkfs.xfs should be updated as follows. Any
>> ideas?
> The intent of the wording in the mkfs man page is "when using a
> custom sector or block size, it must be specified before any
> parameter that uses units of sector or block sizes." So just
> removing the "it must be specified first" wording is incorrect
> because mkfs should throw errors is it is not specified first.
>
>> diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
>> index 4b8c78c..45d7a84 100644
>> --- a/man/man8/mkfs.xfs.8
>> +++ b/man/man8/mkfs.xfs.8
>> @@ -115,9 +115,7 @@ When specifying parameters in units of sectors or
>> filesystem blocks, the
>> .B \-s
>> option or the
>> .B \-b
>> -option first needs to be added to the command line.
>> -Failure to specify the size of the units will result in illegal value
>> errors
>> -when parameters are quantified in those units.
>> +option can be used to specify the size of the sector or block. If the size
>> of the block or sector is not specified, the default size (block: 4KiB,
>> sector: 512B) will be used.
> That's fine to remove.
>
>> .PP
>> Many feature options allow an optional argument of 0 or 1, to explicitly
>> disable or enable the functionality.
>> @@ -136,10 +134,6 @@ The filesystem block size is specified with a
>> in bytes. The default value is 4096 bytes (4 KiB), the minimum is 512, and
>> the
>> maximum is 65536 (64 KiB).
>> .IP
>> -To specify any options on the command line in units of filesystem blocks,
>> this
>> -option must be specified first so that the filesystem block size is
>> -applied consistently to all options.
> "If a non-default filesystem block size is specified, the option
> must be specified before any options that use filesystem block size
> units so that the non-default filesystem block size is applied
> consistently to all options."
>
>> -.IP
>> Although
>> .B mkfs.xfs
>> will accept any of these values and create a valid filesystem,
>> @@ -894,10 +888,6 @@ is 512 bytes. The minimum value for sector size is
>> .I sector_size
>> must be a power of 2 size and cannot be made larger than the
>> filesystem block size.
>> -.IP
>> -To specify any options on the command line in units of sectors, this
>> -option must be specified first so that the sector size is
>> -applied consistently to all options.
> Same wording as for the filesystem block size applies to sector
> sizes as well.
>
> Cheers,
>
> Dave.
Thanks for your suggestions, I will send a updated patch. :)
Best regards,
Alvin
prev parent reply other threads:[~2019-06-13 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 5:20 [PATCH xfsprogs manual] Inconsistency between the code and the manual page Alvin Zheng
2019-06-12 6:47 ` Darrick J. Wong
2019-06-12 22:19 ` Dave Chinner
2019-06-13 10:23 ` Alvin Zheng [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=39ccf3a5-a191-847a-1d68-67e040edc4ed@linux.alibaba.com \
--to=alvin@linux.alibaba.com \
--cc=caspar@linux.alibaba.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--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