From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/4] xfs: disable reaping in fscounters scrub
Date: Thu, 27 Apr 2023 21:28:27 -0700 [thread overview]
Message-ID: <20230428042827.GI59213@frogsfrogsfrogs> (raw)
In-Reply-To: <20230428022041.GT3223426@dread.disaster.area>
On Fri, Apr 28, 2023 at 12:20:41PM +1000, Dave Chinner wrote:
> On Thu, Apr 27, 2023 at 03:49:37PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > The fscounters scrub code doesn't work properly because it cannot
> > quiesce updates to the percpu counters in the filesystem, hence it
> > returns false corruption reports. This has been fixed properly in
> > one of the online repair patchsets that are under review by replacing
> > the xchk_disable_reaping calls with an exclusive filesystem freeze.
> > Disabling background gc isn't sufficient to fix the problem.
> >
> > In other words, scrub doesn't need to call xfs_inodegc_stop, which is
> > just as well since it wasn't correct to allow scrub to call
> > xfs_inodegc_start when something else could be calling xfs_inodegc_stop
> > (e.g. trying to freeze the filesystem).
> >
> > Neuter the scrubber for now, and remove the xchk_*_reaping functions.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
>
> Looks ok, minor nit below.
>
> > @@ -453,6 +446,9 @@ xchk_fscounters(
> > if (frextents > mp->m_sb.sb_rextents)
> > xchk_set_corrupt(sc);
> >
> > + /* XXX: We can't quiesce percpu counter updates, so exit early. */
> > + return 0;
>
> Can you just add to this that we can re-enable this functionality
> when we have the exclusive freeze functionality in the kernel?
Will do.
--D
> With that,
>
> Reviewed-by: Dave Chinner <dchinner@redhat.com>
>
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2023-04-28 4:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 22:49 [PATCHSET 0/4] xfs: inodegc fixes for 6.4-rc1 Darrick J. Wong
2023-04-27 22:49 ` [PATCH 1/4] xfs: explicitly specify cpu when forcing inodegc delayed work to run immediately Darrick J. Wong
2023-04-28 2:14 ` Dave Chinner
2023-04-27 22:49 ` [PATCH 2/4] xfs: check that per-cpu inodegc workers actually run on that cpu Darrick J. Wong
2023-04-28 2:18 ` Dave Chinner
2023-04-27 22:49 ` [PATCH 3/4] xfs: disable reaping in fscounters scrub Darrick J. Wong
2023-04-28 2:20 ` Dave Chinner
2023-04-28 4:28 ` Darrick J. Wong [this message]
2023-04-27 22:49 ` [PATCH 4/4] xfs: fix xfs_inodegc_stop racing with mod_delayed_work Darrick J. Wong
2023-04-28 2:29 ` Dave Chinner
2023-04-28 4:28 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2023-05-01 18:27 [PATCHSET v2 0/4] xfs: inodegc fixes for 6.4-rc1 Darrick J. Wong
2023-05-01 18:27 ` [PATCH 3/4] xfs: disable reaping in fscounters scrub 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=20230428042827.GI59213@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=david@fromorbit.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).