From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org, hch@lst.de
Subject: [PATCHSET v29.2 6/7] xfs: indirect health reporting
Date: Mon, 29 Jan 2024 21:03:34 -0800 [thread overview]
Message-ID: <170659064262.3354229.596649174411799386.stgit@frogsfrogsfrogs> (raw)
Hi all,
This series enables the XFS health reporting infrastructure to remember
indirect health concerns when resources are scarce. For example, if a
scrub notices that there's something wrong with an inode's metadata but
memory reclaim needs to free the incore inode, we want to record in the
perag data the fact that there was some inode somewhere with an error.
The perag structures never go away.
The first two patches in this series set that up, and the third one
provides a means for xfs_scrub to tell the kernel that it can forget the
indirect problem report.
If you're going to start using this code, I strongly recommend pulling
from my git trees, which are linked below.
This has been running on the djcloud for months with no problems. 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=indirect-health-reporting
xfsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=indirect-health-reporting
---
Commits in this patchset:
* xfs: add secondary and indirect classes to the health tracking system
* xfs: remember sick inodes that get inactivated
* xfs: update health status if we get a clean bill of health
---
fs/xfs/libxfs/xfs_fs.h | 4 ++
fs/xfs/libxfs/xfs_health.h | 47 +++++++++++++++++++++++++
fs/xfs/libxfs/xfs_inode_buf.c | 2 +
fs/xfs/scrub/health.c | 76 ++++++++++++++++++++++++++++++++++++++++-
fs/xfs/scrub/health.h | 1 +
fs/xfs/scrub/repair.c | 1 +
fs/xfs/scrub/scrub.c | 6 +++
fs/xfs/scrub/trace.h | 4 ++
fs/xfs/xfs_health.c | 27 ++++++++++-----
fs/xfs/xfs_inode.c | 35 +++++++++++++++++++
fs/xfs/xfs_trace.h | 1 +
11 files changed, 191 insertions(+), 13 deletions(-)
next reply other threads:[~2024-01-30 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 5:03 Darrick J. Wong [this message]
2024-01-30 5:12 ` [PATCH 1/3] xfs: add secondary and indirect classes to the health tracking system Darrick J. Wong
2024-01-30 5:12 ` [PATCH 2/3] xfs: remember sick inodes that get inactivated Darrick J. Wong
2024-01-30 5:12 ` [PATCH 3/3] xfs: update health status if we get a clean bill of 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=170659064262.3354229.596649174411799386.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=hch@lst.de \
--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.