From: Yong Sun <yosun@suse.com>
To: linux-xfs@vger.kernel.org
Cc: yosun <yosun@suse.com>
Subject: [PATCH] xfstests/btrfs: adapt ppc64le node size at least 65536
Date: Fri, 1 Jun 2018 15:57:02 +0800 [thread overview]
Message-ID: <20180601075702.12467-1-yosun@suse.com> (raw)
From: yosun <yosun@suse.com>
node size(leaf size) in ppc64le at least 65536, so mkfs with --nodesize smaller than that number will cause a fail on 057 and 122.
Signed-off-by: Yong Sun <yosun@suse.com>
---
tests/btrfs/057 | 6 ++++++
tests/btrfs/122 | 8 +++++++-
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/tests/btrfs/057 b/tests/btrfs/057
index a834b763..69d096fb 100755
--- a/tests/btrfs/057
+++ b/tests/btrfs/057
@@ -48,6 +48,12 @@ _require_scratch
rm -f $seqres.full
+# the nodesize in ppc64le is at least 65536, it will mismatch output
+HARDWARE_PLATFORM=`uname -i`
+if [ "$HARDWARE_PLATFORM" = "ppc64le" ]; then
+ _notrun "Not supported on ppc64le with nodesize > 4096"
+fi
+
# use small leaf size to get higher btree height.
run_check _scratch_mkfs "-b 1g --nodesize 4096"
diff --git a/tests/btrfs/122 b/tests/btrfs/122
index 213a27f8..50003ad0 100755
--- a/tests/btrfs/122
+++ b/tests/btrfs/122
@@ -55,7 +55,13 @@ rm -f $seqres.full
# Force a small leaf size to make it easier to blow out our root
# subvolume tree
-_scratch_mkfs "--nodesize 16384" >/dev/null
+# Exception: leaf size at least 65536 in ppc64le
+HARDWARE_PLATFORM=`uname -i`
+if [ "$HARDWARE_PLATFORM" = "ppc64le" ]; then
+ _scratch_mkfs "--nodesize 65536" >/dev/null
+else
+ _scratch_mkfs "--nodesize 16384" >/dev/null
+fi
_scratch_mount
_run_btrfs_util_prog quota enable $SCRATCH_MNT
--
2.13.6
next reply other threads:[~2018-06-01 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 7:57 Yong Sun [this message]
2018-06-01 8:06 ` [PATCH] xfstests/btrfs: adapt ppc64le node size at least 65536 Amir Goldstein
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=20180601075702.12467-1-yosun@suse.com \
--to=yosun@suse.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