From: "Darrick J. Wong" <djwong@kernel.org>
To: guaneryu@gmail.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCH v1.1 1/2] common/xfs: support realtime devices with _scratch_xfs_admin
Date: Thu, 25 Mar 2021 16:19:32 -0700 [thread overview]
Message-ID: <20210325231932.GL1670408@magnolia> (raw)
In-Reply-To: <161647323723.3431002.10715201555327186329.stgit@magnolia>
From: Darrick J. Wong <djwong@kernel.org>
Teach _scratch_xfs_admin to support passing the realtime device to
xfs_admin so that we can actually test xfs_admin functionality with
those setups.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
---
v1.1: fix rt_ops variable naming problems
---
common/xfs | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/common/xfs b/common/xfs
index f5e98c1e..06989d1c 100644
--- a/common/xfs
+++ b/common/xfs
@@ -269,9 +269,15 @@ _test_xfs_db()
_scratch_xfs_admin()
{
local options=("$SCRATCH_DEV")
+ local rt_opts=()
[ "$USE_EXTERNAL" = yes -a ! -z "$SCRATCH_LOGDEV" ] && \
options+=("$SCRATCH_LOGDEV")
- $XFS_ADMIN_PROG "$@" "${options[@]}"
+ if [ "$USE_EXTERNAL" = yes ] && [ -n "$SCRATCH_RTDEV" ]; then
+ $XFS_ADMIN_PROG --help 2>&1 | grep -q 'rtdev' || \
+ _notrun 'xfs_admin does not support rt devices'
+ rt_opts+=(-r "$SCRATCH_RTDEV")
+ fi
+ $XFS_ADMIN_PROG "${rt_opts[@]}" "$@" "${options[@]}"
}
_scratch_xfs_logprint()
next prev parent reply other threads:[~2021-03-25 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 4:20 [PATCHSET 0/2] fstests: make sure NEEDSREPAIR feature stops mounts Darrick J. Wong
2021-03-23 4:20 ` [PATCH 1/2] common/xfs: support realtime devices with _scratch_xfs_admin Darrick J. Wong
2021-03-25 17:50 ` Darrick J. Wong
2021-03-25 23:19 ` Darrick J. Wong [this message]
2021-03-23 4:20 ` [PATCH 2/2] xfs: test that the needsrepair feature works as advertised Darrick J. Wong
2021-03-25 23:20 ` [PATCH 3/2] common/xfs: work around a hang-on-stdin bug in xfs_admin 5.11 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=20210325231932.GL1670408@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.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