From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: [PATCHSET v29.4 04/13] xfs: create temporary files for online repair
Date: Mon, 26 Feb 2024 18:18:06 -0800 [thread overview]
Message-ID: <170900012206.938660.3603038404932438747.stgit@frogsfrogsfrogs> (raw)
Hi all,
As mentioned earlier, the repair strategy for file-based metadata is to
build a new copy in a temporary file and swap the file fork mappings
with the metadata inode. We've built the atomic extent swap facility,
so now we need to build a facility for handling private temporary files.
The first step is to teach the filesystem to ignore the temporary files.
We'll mark them as PRIVATE in the VFS so that the kernel security
modules will leave it alone. The second step is to add the online
repair code the ability to create a temporary file and reap extents from
the temporary file after the extent swap.
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=repair-tempfiles
---
Commits in this patchset:
* xfs: hide private inodes from bulkstat and handle functions
* xfs: create temporary files and directories for online repair
* xfs: refactor live buffer invalidation for repairs
* xfs: add the ability to reap entire inode forks
---
fs/xfs/Makefile | 1
fs/xfs/scrub/parent.c | 2
fs/xfs/scrub/reap.c | 445 +++++++++++++++++++++++++++++++++++++++++++++--
fs/xfs/scrub/reap.h | 21 ++
fs/xfs/scrub/scrub.c | 3
fs/xfs/scrub/scrub.h | 4
fs/xfs/scrub/tempfile.c | 251 +++++++++++++++++++++++++++
fs/xfs/scrub/tempfile.h | 28 +++
fs/xfs/scrub/trace.h | 96 ++++++++++
fs/xfs/xfs_export.c | 2
fs/xfs/xfs_inode.c | 3
fs/xfs/xfs_inode.h | 2
fs/xfs/xfs_itable.c | 8 +
13 files changed, 840 insertions(+), 26 deletions(-)
create mode 100644 fs/xfs/scrub/tempfile.c
create mode 100644 fs/xfs/scrub/tempfile.h
next reply other threads:[~2024-02-27 2:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 2:18 Darrick J. Wong [this message]
2024-02-27 2:24 ` [PATCH 1/4] xfs: hide private inodes from bulkstat and handle functions Darrick J. Wong
2024-02-27 18:15 ` Christoph Hellwig
2024-02-28 16:52 ` Darrick J. Wong
2024-02-28 17:02 ` Christoph Hellwig
2024-02-28 17:33 ` Darrick J. Wong
2024-02-28 17:39 ` Christoph Hellwig
2024-02-27 2:25 ` [PATCH 2/4] xfs: create temporary files and directories for online repair Darrick J. Wong
2024-02-27 18:16 ` Christoph Hellwig
2024-02-27 2:25 ` [PATCH 3/4] xfs: refactor live buffer invalidation for repairs Darrick J. Wong
2024-02-27 18:16 ` Christoph Hellwig
2024-02-27 2:25 ` [PATCH 4/4] xfs: add the ability to reap entire inode forks Darrick J. Wong
2024-02-27 18:16 ` Christoph Hellwig
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=170900012206.938660.3603038404932438747.stgit@frogsfrogsfrogs \
--to=djwong@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 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.