From: Richard Wareing <rwareing@fb.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH 0/3] Fix/harden "quick" tests for realtime subvolumes
Date: Thu, 21 Sep 2017 19:02:37 -0700 [thread overview]
Message-ID: <20170922020240.2503987-1-rwareing@fb.com> (raw)
Some tests have issues when being run with realtime subvolumes. This patch
set aims to harden fs tests so we can get reliable/reproducible test runs
with fstests for realtime subvolumes.
Two new _require functions are introduced along with a new flag to
automatically set the rtinherit=1 option upon mkfs'ing.
The problems I found were usually one of:
1. Snapshot + subsequent test being performed without regard to the realtime
subvolume.
2. Use of functions which are not supported by realtime devices. Not setting
rtinherit on scratch devices for these cases fixes these tests. Non-scratch
cases are more tricky since we don't control what goes into the MKFS_OPTIONS
variable.
3. xfs_repair being used directly without checking for RT devices.
After fixing these cases, you get 86 good "quick: xfs tests & 180 good "quick"
generic tests with the bulk are not run due to the lack of reflink and/or quota
support on realtime scratch targets.
P.S. I haven't forgotten about the non-"quick" tests, but I had to start
somewhere, and break this up a bit into a more manageable problem.
Richard Wareing (3):
xfs/realtime: Add require_no_realtime function
xfs/realtime: Default rtinherit=1, add _require_no_rtinherit function
xfs/realtime: Fix direct invocations of xfs_repair
common/rc | 32 +++++++++++++++++++++++++++++++-
tests/generic/250 | 1 +
tests/generic/252 | 1 +
tests/generic/409 | 1 +
tests/generic/410 | 1 +
tests/generic/411 | 1 +
tests/generic/427 | 1 +
tests/generic/441 | 1 +
tests/xfs/019 | 1 +
tests/xfs/031 | 1 +
tests/xfs/070 | 4 ++--
tests/xfs/077 | 1 +
tests/xfs/170 | 1 +
tests/xfs/187 | 1 +
tests/xfs/189 | 1 +
tests/xfs/191-input-validation | 1 +
tests/xfs/202 | 1 +
tests/xfs/284 | 1 +
tests/xfs/291 | 3 ++-
19 files changed, 51 insertions(+), 4 deletions(-)
--
2.9.5
next reply other threads:[~2017-09-22 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 2:02 Richard Wareing [this message]
2017-09-22 2:02 ` [PATCH 1/3] xfs/realtime: Add require_no_realtime function Richard Wareing
2017-09-22 2:02 ` [PATCH 2/3] xfs/realtime: Default rtinherit=1, add _require_no_rtinherit function Richard Wareing
2017-09-22 2:02 ` [PATCH 3/3] xfs/realtime: Fix direct invocations of xfs_repair Richard Wareing
2017-09-22 19:00 ` Darrick J. Wong
2017-09-22 19:15 ` Richard Wareing
2017-09-22 2:18 ` [PATCH 0/3] Fix/harden "quick" tests for realtime subvolumes Richard Wareing
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=20170922020240.2503987-1-rwareing@fb.com \
--to=rwareing@fb.com \
--cc=fstests@vger.kernel.org \
--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