From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanrlinux@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
greg.marsden@oracle.com, shirley.ma@oracle.com,
konrad.wilk@oracle.com, Matthew Wilcox <willy@infradead.org>,
Dave Chinner <david@fromorbit.com>,
Catherine Hoang <catherine.hoang@oracle.com>,
fstests <fstests@vger.kernel.org>, Zorro Lang <zlang@redhat.com>,
Carlos Maiolino <cmaiolino@redhat.com>,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: [NYE PATCHRIVER 1/4] xfs: the rest of online repair part 1
Date: Sun, 31 Dec 2023 10:12:15 -0800 [thread overview]
Message-ID: <20231231181215.GA241128@frogsfrogsfrogs> (raw)
Hi everyone,
In last year's NYE deluges, I mentioned that I wanted to get online
repair merged for the 2023 LTS kernel. That goal was not attained, so
now I want to get this merged in time for the 2024 LTS kernel.
(Big thanks to Dave earlier for helping to get all 120 scrub fixes
merged; and Christoph more recently for doing the same for the first 30
patches of repair and a bunch of rt refactorings from the modernization
series.)
But seriously, folks, this is dragging on unnecessarily. Either you all
need to step up and actually review the 55 patchsets and 458 patches
needed to get online repair done, or decide to let me merge it and deal
with the consequences, which I will. The only part of this deluge that
changes the ondisk format are the swapext patches that add a new log
intent item type. Everything else is guarded by Kconfig options and
won't destabilize the rest of the filesystem. I haven't changed the
swapext log intent item format since 2021. 2+ years to get feedback is
dysfunctional.
In the meantime, lack of upstream merging means that I cannot start
wider testing of this code with the people who run (b)leading edge XFS
code; I cannot solicit user and customer feedback because they don't
have the code; and there's no way I can meaningfully prioritize
improvements to the code because **I cannot get feedback**.
Fuzz and stress testing of online repairs have been running well for two
years now. As of this writing, online repair can fix more things than
offline repair, and the fsstress+repair long soak test has passed 300
million repairs with zero problems observed.
(For comparison, the long soak fsx test recently passed 110 billion file
operations, so online fsck has a ways to go...)
--D
next reply other threads:[~2023-12-31 18:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 18:12 Darrick J. Wong [this message]
2023-12-31 19:57 ` [PATCHSET 1/8] fstests: fuzz non-root dquots on xfs Darrick J. Wong
2023-12-27 13:42 ` [PATCH 1/3] fuzzy: mask off a few more inode fields from the fuzz tests Darrick J. Wong
2023-12-27 13:43 ` [PATCH 2/3] fuzzy: allow FUZZ_REWRITE_DURATION to control fsstress runtime when fuzzing Darrick J. Wong
2023-12-27 13:43 ` [PATCH 3/3] fuzzy: test other dquot ids Darrick J. Wong
2023-12-31 19:57 ` [PATCHSET 2/8] xfsprogs: scale shards on ssds Darrick J. Wong
2023-12-27 13:43 ` [PATCH 1/1] xfs: test scaling of the mkfs concurrency options Darrick J. Wong
2023-12-31 19:57 ` [PATCHSET v29.0 3/8] fstests: establish baseline for fuzz tests Darrick J. Wong
2023-12-27 13:43 ` [PATCH 1/4] xfs: online fuzz test known output Darrick J. Wong
2023-12-27 13:44 ` [PATCH 2/4] xfs: offline " Darrick J. Wong
2023-12-27 13:44 ` [PATCH 3/4] xfs: norepair " Darrick J. Wong
2023-12-27 13:44 ` [PATCH 4/4] xfs: bothrepair " Darrick J. Wong
2023-12-31 19:57 ` [PATCHSET v29.0 4/8] fstests: atomic file updates Darrick J. Wong
2023-12-27 13:44 ` [PATCH 1/1] swapext: make sure that we don't swap unwritten extents unless they're part of a rt extent(??) Darrick J. Wong
2023-12-31 19:58 ` [PATCHSET v29.0 5/8] fstests: detect deceptive filename extensions Darrick J. Wong
2023-12-27 13:45 ` [PATCH 1/2] generic/453: test confusable name detection with 32-bit unicode codepoints Darrick J. Wong
2023-12-27 13:45 ` [PATCH 2/2] generic/453: check xfs_scrub detection of confusing job offers Darrick J. Wong
2023-12-31 19:58 ` [PATCHSET v29.0 6/8] fstests: test systemd background services Darrick J. Wong
2023-12-27 13:45 ` [PATCH 1/1] xfs: test xfs_scrub services Darrick J. Wong
2023-12-31 19:58 ` [PATCHSET v29.0 7/8] fstests: use free space histograms to reduce fstrim runtime Darrick J. Wong
2023-12-27 13:45 ` [PATCH 1/1] xfs/004: fix column extraction code Darrick J. Wong
2023-12-31 19:58 ` [PATCHSET 8/8] fstests: test upgrading older features Darrick J. Wong
2023-12-27 13:46 ` [PATCH 1/1] xfs: test upgrading old features 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=20231231181215.GA241128@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=catherine.hoang@oracle.com \
--cc=chandanrlinux@gmail.com \
--cc=cmaiolino@redhat.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=greg.marsden@oracle.com \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=konrad.wilk@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=shirley.ma@oracle.com \
--cc=willy@infradead.org \
--cc=zlang@redhat.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