From: "Darrick J. Wong" <djwong@kernel.org>
To: dchinner@redhat.com, Carlos Maiolino <cem@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Shirley Ma <shirley.ma@oracle.com>,
Greg Marsden <greg.marsden@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Allison Henderson <allison.henderson@oracle.com>,
Catherine Hoang <catherine.hoang@oracle.com>
Subject: [ANNOUNCE] xfs: online repair is completely finished!
Date: Mon, 21 Aug 2023 17:22:04 -0700 [thread overview]
Message-ID: <20230822002204.GA11263@frogsfrogsfrogs> (raw)
Hi folks,
I am /very/ pleased to announce that online repair for XFS is completely
finished. For those of you who have been following along all this time,
this means that part 1 and part 2 are done!
With the addition in part 2 of directory parent pointers patchset,
xfs_scrub gains the ability to correct broken links and loops in the
directory tree. Part 2 also adds a faster FITRIM implementation,
improved detection of malicious filenames, and a vectorized scrub mode
that cuts the runtime by 20%.
Code coverage averages around ~75% for the online fsck code (and ~85%
for the rest of XFS), and the kernel can now rebuild 90% of the
corruptions that can manifest on a mountable filesystem.
The code itself lives in my git trees, which I've just updated:
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/log/?h=vectorized-scrub
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=vectorized-scrub
https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfstests-dev.git/log/?h=scrub-directory-tree
As I have now been testing online repair in its various stages [on my
testing cloud] for two years and the fstests cloud has nearly cleared
300 million successful filesystem repairs, I am discontinuing all
notices about "This is an extraordinary way to destroy your data".
It works, and it's time to merge it to get broader testing.
A big thank you to Allison Henderson, Catherine Hoang for their work on
the directory parent pointers feature; Chandan Babu for reviewing the
design documentation; and Dave Chinner and Matthew Wilcox for staring
at the code longer than is probably healthy. 8-)
Stay tuned for more exciting announcements!
--Darrick
next reply other threads:[~2023-08-22 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 0:22 Darrick J. Wong [this message]
2023-08-28 12:33 ` [ANNOUNCE] xfs: online repair is completely finished! Emmanuel Florac
2023-09-01 14:54 ` 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=20230822002204.GA11263@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=catherine.hoang@oracle.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=greg.marsden@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=shirley.ma@oracle.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).