From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH 5/5] xfs: scrub should only cross-reference with healthy btrees
Date: Tue, 16 Apr 2019 11:16:00 +1000 [thread overview]
Message-ID: <20190416011600.GK29573@dread.disaster.area> (raw)
In-Reply-To: <155537400192.27935.5071586825961103642.stgit@magnolia>
On Mon, Apr 15, 2019 at 05:20:01PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Skip cross-referencing with a btree if the health report tells us that
> it's known to be bad. This should reduce the dmesg spew considerably.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
....
> --- a/fs/xfs/scrub/health.c
> +++ b/fs/xfs/scrub/health.c
> @@ -174,3 +174,79 @@ xchk_update_health(
> break;
> }
> }
> +
> +/* Is the given per-AG btree healthy enough for scanning? */
> +bool
> +xchk_ag_btree_healthy_enough(
> + struct xfs_scrub *sc,
> + struct xfs_perag *pag,
> + xfs_btnum_t btnum)
> +{
> + unsigned int mask = 0;
> +
> + /*
> + * We always want the cursor if it's the same type as whatever we're
> + * scrubbing, even if we already know the structure is corrupt.
> + */
> + switch (sc->sm->sm_type) {
> + case XFS_SCRUB_TYPE_BNOBT:
> + if (btnum == XFS_BTNUM_BNO)
> + return true;
> + break;
> + case XFS_SCRUB_TYPE_CNTBT:
> + if (btnum == XFS_BTNUM_CNT)
> + return true;
> + break;
> + case XFS_SCRUB_TYPE_INOBT:
> + if (btnum == XFS_BTNUM_INO)
> + return true;
> + break;
> + case XFS_SCRUB_TYPE_FINOBT:
> + if (btnum == XFS_BTNUM_FINO)
> + return true;
> + break;
> + case XFS_SCRUB_TYPE_RMAPBT:
> + if (btnum == XFS_BTNUM_RMAP)
> + return true;
> + break;
> + case XFS_SCRUB_TYPE_REFCNTBT:
> + if (btnum == XFS_BTNUM_REFC)
> + return true;
> + break;
> + }
> +
> + /*
> + * Otherwise, we're only interested in the btree for cross-referencing.
> + * If we know the btree is bad then don't bother, just set XFAIL.
> + */
> + switch (btnum) {
> + case XFS_BTNUM_BNO:
> + mask = XFS_SICK_AG_BNOBT;
> + break;
> + case XFS_BTNUM_CNT:
> + mask = XFS_SICK_AG_CNTBT;
> + break;
> + case XFS_BTNUM_INO:
> + mask = XFS_SICK_AG_INOBT;
> + break;
> + case XFS_BTNUM_FINO:
> + mask = XFS_SICK_AG_FINOBT;
> + break;
> + case XFS_BTNUM_RMAP:
> + mask = XFS_SICK_AG_RMAPBT;
> + break;
> + case XFS_BTNUM_REFC:
> + mask = XFS_SICK_AG_REFCNTBT;
> + break;
> + default:
> + ASSERT(0);
> + return true;
> + }
> +
> + if (xfs_ag_has_sickness(pag, mask)) {
> + sc->sm->sm_flags |= XFS_SCRUB_OFLAG_XFAIL;
> + return false;
> + }
> +
> + return true;
THis could be done with a single switch statement:
switch (btnum) {
case XFS_BTNUM_BNO:
if (sc->sm->sm_type == XFS_SCRUB_TYPE_BNOBT)
return true;
mask = XFS_SICK_AG_BNOBT;
break;
case XFS_BTNUM_CNT:
if (sc->sm->sm_type == XFS_SCRUB_TYPE_CNTBT)
return true;
mask = XFS_SICK_AG_CNTBT;
break;
.....
Otherwise it is fine.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-04-16 1:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 0:19 [PATCH v3 0/5] xfs: scrub/repair update health tracking Darrick J. Wong
2019-04-16 0:19 ` [PATCH 1/5] xfs: refactor scrub context initialization Darrick J. Wong
2019-04-16 0:47 ` Dave Chinner
2019-04-16 0:19 ` [PATCH 2/5] xfs: collapse scrub bool state flags into a single unsigned int Darrick J. Wong
2019-04-16 0:49 ` Dave Chinner
2019-04-16 0:19 ` [PATCH 3/5] xfs: hoist the already_fixed variable to the scrub context Darrick J. Wong
2019-04-16 0:51 ` Dave Chinner
2019-04-16 0:54 ` Darrick J. Wong
2019-04-16 0:19 ` [PATCH 4/5] xfs: scrub/repair should update filesystem metadata health Darrick J. Wong
2019-04-16 1:09 ` Dave Chinner
2019-04-16 1:31 ` Darrick J. Wong
2019-04-16 1:43 ` [PATCH v2 " Darrick J. Wong
2019-04-16 7:57 ` Dave Chinner
2019-04-16 0:20 ` [PATCH 5/5] xfs: scrub should only cross-reference with healthy btrees Darrick J. Wong
2019-04-16 1:16 ` Dave Chinner [this message]
2019-04-16 1:45 ` [PATCH v2 " Darrick J. Wong
2019-04-16 7:58 ` Dave Chinner
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=20190416011600.GK29573@dread.disaster.area \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=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