From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/4] xfs: scrub/repair update health tracking
Date: Wed, 10 Apr 2019 18:46:19 -0700 [thread overview]
Message-ID: <155494717912.1090718.9199703658765720229.stgit@magnolia> (raw)
Hi all,
This series enhances the online scrub and repair code to report their
findings to the health tracking subsystem. For now, only scrub gets to
record corruption problems, though in principle a metadata read
encountering corruption could also set a sick flag.
Online repair will clear the appropriate sick flags when metadata passes
its inspection after a repair attempt.
On the userspace side of things, xfs_scrub will be adapted to give a
clean bill of health to the kernel when it is warranted.
The first three patches rework the scrub context management code to
remove some clunkiness when we decide that we have to start the scrub
over.
Patch #4 actually teaches scrub to update the health subsystem.
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
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=scrub-health-tracking
next reply other threads:[~2019-04-11 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 1:46 Darrick J. Wong [this message]
2019-04-11 1:46 ` [PATCH 1/4] xfs: refactor scrub context initialization Darrick J. Wong
2019-04-11 1:46 ` [PATCH 2/4] xfs: collapse scrub bool state flags into a single unsigned int Darrick J. Wong
2019-04-11 1:46 ` [PATCH 3/4] xfs: hoist the already_fixed variable to the scrub context Darrick J. Wong
2019-04-11 1:46 ` [PATCH 4/4] xfs: scrub/repair should update filesystem metadata health 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=155494717912.1090718.9199703658765720229.stgit@magnolia \
--to=darrick.wong@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.