From: Lukas Herbolt <lukas@herbolt.com>
To: zlang@kernel.org, djwong@kernel.org
Cc: fstests@vger.kernel.org, xfs-linux@kernel.org,
Lukas Herbolt <lukas@herbolt.com>
Subject: [PATCH v2 4/4] xfs/21{6,7} Use default -l concurrency=0 on mkfs.xfs that supports it
Date: Thu, 14 May 2026 13:39:15 +0200 [thread overview]
Message-ID: <20260514113910.866888-10-lukas@herbolt.com> (raw)
In-Reply-To: <20260514113910.866888-2-lukas@herbolt.com>
The XFS concurrency optimization breaks the log sizing check on
systems with non-rotational disks and high amount of CPUs. Default to
the old behavior with -l concurrency=0 and with -d concurrency=0.
Signed-off-by: Lukas Herbolt <lukas@herbolt.com>
---
changes v2:
use default mkfs.xfs for scratch device
remove the double check -l/-d as those were introduced together
tests/xfs/216 | 6 +++++-
tests/xfs/217 | 7 ++++++-
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/tests/xfs/216 b/tests/xfs/216
index 091c11d08642..0148e7f4de3e 100755
--- a/tests/xfs/216
+++ b/tests/xfs/216
@@ -22,13 +22,17 @@ _cleanup()
_require_scratch
_scratch_mkfs_xfs >/dev/null 2>&1
+if _scratch_mkfs_xfs_supports_concurrency -l >> $seqres.full 2>&1; then
+ loop_mkfs_opts="-l concurrency=0"
+else
+ loop_mkfs_opts=""
+fi
_scratch_mount
_require_loop
LOOP_IMG=$SCRATCH_MNT/test_fs
LOOP_MNT=$SCRATCH_MNT/test_fs_dir
-loop_mkfs_opts=
$MKFS_XFS_PROG 2>&1 | grep -q rmapbt && \
loop_mkfs_opts="$loop_mkfs_opts -m rmapbt=0"
$MKFS_XFS_PROG 2>&1 | grep -q reflink && \
diff --git a/tests/xfs/217 b/tests/xfs/217
index dae6ce55f475..23aae842d1fb 100755
--- a/tests/xfs/217
+++ b/tests/xfs/217
@@ -21,6 +21,11 @@ _cleanup()
_require_scratch
_scratch_mkfs_xfs >/dev/null 2>&1
+if _scratch_mkfs_xfs_supports_concurrency -l >> $seqres.full 2>&1; then
+ loop_mkfs_opts="-l concurrency=0 -d concurrency=0"
+else
+ loop_mkfs_opts=""
+fi
_scratch_mount
# 16T mkfs requires a bit over 2G free
_require_fs_space $SCRATCH_MNT 2202000
@@ -34,7 +39,7 @@ _do_mkfs()
for i in $*; do
echo -n "fssize=${i}g "
$MKFS_XFS_PROG -f -b size=4096 -l version=2 \
- -d size=${i}g $loop_dev |grep log
+ -d size=${i}g $loop_dev $loop_mkfs_opts |grep log
_mount $loop_dev $LOOP_MNT
echo "test write" > $LOOP_MNT/test
_unmount $LOOP_MNT > /dev/null 2>&1
--
2.54.0
next prev parent reply other threads:[~2026-05-14 11:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 11:39 [PATCH v2 0/4] Fixes for mkfs.xfs with high amount of CPUs and SSDs Lukas Herbolt
2026-05-14 11:39 ` [PATCH v2 1/4] common/rc: Add helper to calculate percentage of free space available Lukas Herbolt
2026-05-14 14:45 ` Darrick J. Wong
2026-05-15 15:59 ` Zorro Lang
2026-05-14 11:39 ` [PATCH v2 2/4] common/xfs: helper function to check if -l/-d/-r concurrecy flags Lukas Herbolt
2026-05-14 14:46 ` Darrick J. Wong
2026-05-15 16:03 ` Zorro Lang
2026-05-14 11:39 ` [PATCH v2 3/4] generic/{102,172,347}: Adapt test for XFS on systems with 128+CPUs + SSDs Lukas Herbolt
2026-05-14 14:46 ` Darrick J. Wong
2026-05-15 16:09 ` Zorro Lang
2026-05-14 11:39 ` Lukas Herbolt [this message]
2026-05-14 14:47 ` [PATCH v2 4/4] xfs/21{6,7} Use default -l concurrency=0 on mkfs.xfs that supports it Darrick J. Wong
2026-05-15 16:18 ` Zorro Lang
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=20260514113910.866888-10-lukas@herbolt.com \
--to=lukas@herbolt.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=xfs-linux@kernel.org \
--cc=zlang@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 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.