From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/9] fstests: btrfs: _scratch_mkfs_sized fix min size without mixed option
Date: Mon, 24 Sep 2018 19:53:13 +0800 [thread overview]
Message-ID: <bdd780f8-8c50-c859-30ba-53c68d81bb72@oracle.com> (raw)
In-Reply-To: <c770f3ed-a813-74c9-0b9d-04a3ce740185@gmx.com>
On 09/24/2018 06:58 PM, Qu Wenruo wrote:
>
>
> On 2018/9/24 下午6:16, Anand Jain wrote:
>> As of now _scratch_mkfs_sized check if the requested size is below 1G
>> and forces the --mixed option for the mkfs.btrfs. Well the correct size
>> at which we need to force the mixed option is 114294784bytes. Fix that.
>
> How this size is get from?
> If it's from btrfs_min_dev_size(), I strongly recommend to add reference
> here, and don't use the ugly intermediate number.
>
>
> BTW, this number is related to mkfs profile.
> If you really want to use some maximum number, please follow the max
> possible value in btrfs_min_dev_size(), which should be 229M other than
> 106M.
Thanks for the comments. I completely missed out the point of other
group profile requiring more than ~115 bytes. Will fix.
Yep the ref for the size is btrfs_min_dev_size().
-Anand
> Thanks,
> Qu
>
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> common/rc | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/common/rc b/common/rc
>> index d5bb1feee2c3..bcdbf03e1bf0 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -969,7 +969,9 @@ _scratch_mkfs_sized()
>> ;;
>> btrfs)
>> local mixed_opt=
>> - (( fssize <= 1024 * 1024 * 1024 )) && mixed_opt='--mixed'
>> + # minimum size that's needed without the mixed option.
>> + # Non mixed mode is also the default option.
>> + (( fssize < 114294784 )) && mixed_opt='--mixed'
>> $MKFS_BTRFS_PROG $MKFS_OPTIONS $mixed_opt -b $fssize $SCRATCH_DEV
>> ;;
>> jfs)
>>
>
next prev parent reply other threads:[~2018-09-24 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 10:16 [PATCH 0/9] Fix _scratch_mkfs_sized() for btrfs Anand Jain
2018-09-24 10:16 ` [PATCH 1/9] fstests: btrfs: _scratch_mkfs_sized fix min size without mixed option Anand Jain
2018-09-24 10:58 ` Qu Wenruo
2018-09-24 11:53 ` Anand Jain [this message]
2018-09-24 12:02 ` Qu Wenruo
2018-09-24 13:40 ` Anand Jain
2018-09-24 10:16 ` [PATCH 2/9] generic/015 fix to test the default non-mixed mode Anand Jain
2018-09-24 11:01 ` Qu Wenruo
2018-09-24 11:55 ` Anand Jain
2018-09-24 10:16 ` [PATCH 3/9] geneirc/077 fix min size for btrfs Anand Jain
2018-09-24 10:16 ` [PATCH 4/9] generic/083 create at least 200mb fs Anand Jain
2018-09-24 10:16 ` [PATCH 5/9] generic/102 open code dev_size _scratch_mkfs_sized() Anand Jain
2018-09-24 10:16 ` [PATCH 6/9] generic/204 open code SIZE for _scratch_mkfs_sized() Anand Jain
2018-09-24 10:16 ` [PATCH 7/9] generic/312 open code fs_size _scratch_mkfs_sized() Anand Jain
2018-09-24 10:16 ` [PATCH 8/9] generic/449 fix fs size for _scratch_mkfs_sized for btrfs Anand Jain
2018-09-24 10:16 ` [PATCH 9/9] generic/387 fix _scratch_mkfs_sized option " Anand Jain
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=bdd780f8-8c50-c859-30ba-53c68d81bb72@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).