From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [XFS SUMMIT] Online Fsck Status Update
Date: Wed, 22 Apr 2020 16:55:59 -0700 [thread overview]
Message-ID: <20200422235559.GK6742@magnolia> (raw)
Hi everyone,
This one is meant to be a status update about where I am with online
repair. The btree bulk loading code went upstream for 5.7, which will
enable us to refactor a lot of boilerplate code out of xfs_repair.
At this point, I have finished fleshing out nearly all of the online
repair functionality. We can rebuild all per-AG btrees and the inode
fork mapping btrees. With the deferred inactivation series and fs
freezing, we can also rebuild the rmapbt and run quotacheck on a frozen
filesystem, which means that quotas can be repaired too.
More recently, I've written repair code for the realtime bitmap and
summary files; and preliminary versions of extended attribute and
directory salvaging. With the new atomic extent swap series, I can now
commit rebuilt metadata atomically.
However, the directory tree reconstruction part is /very/ difficult to
achieve without parent pointers, since we cannot easily reconnect
orphaned files without scanning the entire directory tree under fs
freeze. We also can't do nlink verification easily without parent
pointer validation.
--D
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=scrub-rtsummary
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-ag-btrees
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-inodes
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-inode-data
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-fsfile-metadata
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=repair-metadata-atomically
reply other threads:[~2020-04-22 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200422235559.GK6742@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 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).