From: Ma Xinjian <maxj.fnst@fujitsu.com>
To: zlang@kernel.org
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
Xinjian Ma <maxj.fnst@fujitsu.com>
Subject: [PATCH] xfs/603: add _require_scrub
Date: Tue, 10 Jun 2025 17:11:34 +0800 [thread overview]
Message-ID: <20250610091134.152557-1-maxj.fnst@fujitsu.com> (raw)
From: Xinjian Ma <maxj.fnst@fujitsu.com>
This test uses xfs_scrub which is an EXPERIMENTAL and unstable feature.
Add _require_scrub to check if the system supports it.
Signed-off-by: Xinjian Ma <maxj.fnst@fujitsu.com>
---
tests/xfs/603 | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/xfs/603 b/tests/xfs/603
index 04122b55..d6058a3e 100755
--- a/tests/xfs/603
+++ b/tests/xfs/603
@@ -20,6 +20,7 @@ _require_xfs_db_command iunlink
# until after the directory repair code was merged
_require_xfs_io_command repair -R directory
_require_scratch_nocheck # repair doesn't like single-AG fs
+_require_scrub
# From the AGI definition
XFS_AGI_UNLINKED_BUCKETS=64
--
2.49.0
next reply other threads:[~2025-06-10 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:11 Ma Xinjian [this message]
2025-06-10 14:46 ` [PATCH] xfs/603: add _require_scrub Darrick J. Wong
2025-06-11 12:50 ` Carlos Maiolino
2025-06-11 14:18 ` Darrick J. Wong
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=20250610091134.152557-1-maxj.fnst@fujitsu.com \
--to=maxj.fnst@fujitsu.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox