From: Brian Foster <bfoster@redhat.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v3 0/3] fix up generic dmlogwrites tests to work with XFS
Date: Tue, 1 Sep 2020 09:47:25 -0400 [thread overview]
Message-ID: <20200901134728.185353-1-bfoster@redhat.com> (raw)
Hi all,
This version removes the discard zeroing check as Christoph points out
that discard behavior is generally not predictable. The remaining
generic dm-logwrites tests are still updated to use dm-thinp such that
discards from the recovery tool clear block ranges reasonably reliably.
This allows the tests to function correctly on filesystems like XFS
while a more generic solution is investigated.
Brian
v3:
- Re-add dm-thinp changes.
- Drop discard checks (from v1) and XFS disablement (from v2).
- Use _require_scratch_nocheck in generic/470 to avoid spurious repair
noise now that the test no longer runs mkfs on the scratch dev.
v2: https://lore.kernel.org/fstests/20200827145329.435398-1-bfoster@redhat.com/
- Drop all dmthinp changes. Unconditionally disable tests on XFS.
v1: https://lore.kernel.org/fstests/20200826143815.360002-2-bfoster@redhat.com/
Brian Foster (3):
generic/455: use thin volume for dmlogwrites target device
generic/457: use thin volume for dmlogwrites target device
generic/470: use thin volume for dmlogwrites target device
tests/generic/455 | 36 ++++++++++++++++++++++--------------
tests/generic/457 | 33 +++++++++++++++++++++------------
tests/generic/470 | 23 +++++++++++++++++------
3 files changed, 60 insertions(+), 32 deletions(-)
--
2.25.4
next reply other threads:[~2020-09-01 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 13:47 Brian Foster [this message]
2020-09-01 13:47 ` [PATCH v3 1/3] generic/455: use thin volume for dmlogwrites target device Brian Foster
2020-09-01 14:06 ` Amir Goldstein
2020-09-01 13:47 ` [PATCH v3 2/3] generic/457: " Brian Foster
2020-09-01 14:07 ` Amir Goldstein
2020-09-01 13:47 ` [PATCH v3 3/3] generic/470: " Brian Foster
2020-09-01 14:08 ` 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=20200901134728.185353-1-bfoster@redhat.com \
--to=bfoster@redhat.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;
as well as URLs for NNTP newsgroup(s).