From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Anand Jain <anand.jain@oracle.com>, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs/122: fix nodesize option in mfks.btrfs
Date: Sun, 11 Jun 2023 16:48:56 +0530 [thread overview]
Message-ID: <87cz22i6vz.fsf@doe.com> (raw)
In-Reply-To: <a45349aa46e0b185acf59f3914e78dce245bb696.1685705269.git.anand.jain@oracle.com>
Anand Jain <anand.jain@oracle.com> writes:
> btrf/122 is failing on a system with 64k page size:
>
> QA output created by 122
> +ERROR: illegal nodesize 16384 (smaller than 65536)
> +mount: /mnt/scratch: wrong fs type, bad option, bad superblock on /dev/vdb2, missing codepage or helper program, or other error.
> +mount /dev/vdb2 /mnt/scratch failed
> +(see /xfstests-dev/results//btrfs/122.full for details)
>
> Mkfs.btrfs sets the default node size to 16K when the sector size is less
> than 16K, and it matches the sector size when it's greater than 16K.
> So, there's no need to explicitly set it.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> v2: Remove the redundant explicit nodesize option from mkfs.btrfs.
> Changed: Title from "btrfs/122: adjust nodesize to match pagesize"
>
>
> tests/btrfs/122 | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Thanks for fixing this. I have tested this on Power with 64k pagesize and x86
with 4k pagesize.
Please feel free to add -
Tested-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
-ritesh
prev parent reply other threads:[~2023-06-11 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 13:13 [PATCH] btrfs/122: adjust nodesize to match pagesize Anand Jain
2023-06-01 9:32 ` Zorro Lang
2023-06-02 11:15 ` Anand Jain
2023-06-02 11:38 ` [PATCH v2] btrfs/122: fix nodesize option in mfks.btrfs Anand Jain
2023-06-10 6:57 ` Zorro Lang
2023-06-10 7:03 ` Zorro Lang
2023-06-10 7:56 ` Anand Jain
2023-06-11 11:18 ` Ritesh Harjani [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=87cz22i6vz.fsf@doe.com \
--to=ritesh.list@gmail.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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