From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com, zlang@redhat.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET v23.1 0/1] fstests: test xfs_scrub media scan
Date: Wed, 02 Nov 2022 15:36:15 -0700 [thread overview]
Message-ID: <166742857552.1499365.12368724681885402947.stgit@magnolia> (raw)
Hi all,
Use dm-error to simulate disk errors for written file extents and ensure
that the media scanner in xfs_scrub actually detects them.
v23.1: tidy up some loose ends, make it more obvious in dmerror where the
awk and bash transitions happen
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
xfsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=scrub-media-error-reporting
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=scrub-media-error-reporting
---
common/dmerror | 140 ++++++++++++++++++++++++++++++++++++++++++++++++
common/xfs | 9 +++
tests/xfs/747 | 155 +++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/747.out | 12 ++++
4 files changed, 316 insertions(+)
create mode 100755 tests/xfs/747
create mode 100644 tests/xfs/747.out
next reply other threads:[~2022-11-02 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:36 Darrick J. Wong [this message]
2022-11-02 22:36 ` [PATCH 1/1] xfs: test xfs_scrub phase 6 media error reporting Darrick J. Wong
2022-11-03 3:11 ` Zorro Lang
2022-11-03 4:13 ` Darrick J. Wong
2022-11-03 4:17 ` [PATCH v23.2 " Darrick J. Wong
2022-11-03 5:00 ` Zorro Lang
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 22:45 [PATCHSET v23.1 0/1] fstests: test xfs_scrub media scan 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=166742857552.1499365.12368724681885402947.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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).