From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 6/9] repair: report AG btree verifier errors
Date: Tue, 15 Apr 2014 15:40:48 -0400 [thread overview]
Message-ID: <20140415194048.GD3470@laptop.bfoster> (raw)
In-Reply-To: <1397550301-31883-7-git-send-email-david@fromorbit.com>
On Tue, Apr 15, 2014 at 06:24:58PM +1000, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> When we scan the filesystem freespace and inode maps in phase 2, we
> don't report CRC errors that are found. We don't really care from a
> repair perspective, because the trees are completely rebuilt from
> the ground up in phase 5, but froma checking perspective we need to
> inform the user that we found inconsistencies.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> repair/scan.c | 27 ++++++++++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
> diff --git a/repair/scan.c b/repair/scan.c
> index 6c43474..75b4b70 100644
> --- a/repair/scan.c
> +++ b/repair/scan.c
> @@ -82,6 +82,12 @@ scan_sbtree(
> do_error(_("can't read btree block %d/%d\n"), agno, root);
> return;
> }
> + if (bp->b_error == EFSBADCRC || bp->b_error == EFSCORRUPTED) {
> + do_warn(_("btree block %d/%d is suspect, error %d\n"),
> + agno, root, bp->b_error);
> + suspect = 1;
> + }
> +
> (*func)(XFS_BUF_TO_BLOCK(bp), nlevels - 1, root, agno, suspect,
> isroot, magic, priv);
> libxfs_putbuf(bp);
> @@ -123,6 +129,7 @@ scan_lbtree(
> xfs_buf_t *bp;
> int err;
> int dirty = 0;
> + bool badcrc = false;
>
> bp = libxfs_readbuf(mp->m_dev, XFS_FSB_TO_DADDR(mp, root),
> XFS_FSB_TO_BB(mp, 1), 0, ops);
> @@ -132,14 +139,25 @@ scan_lbtree(
> XFS_FSB_TO_AGBNO(mp, root));
> return(1);
> }
> +
> + /*
> + * only check for bad CRC here - caller will determine if there
> + * is a corruption or not and whether it got corrected and so needs
> + * writing back. CRC errors always imply we need to write the block.
> + */
> + if (bp->b_error == EFSBADCRC) {
> + do_warn(_("btree block %d/%d is suspect, error %d\n"),
> + XFS_FSB_TO_AGNO(mp, root),
> + XFS_FSB_TO_AGBNO(mp, root), bp->b_error);
> + badcrc = true;
> + }
> +
> err = (*func)(XFS_BUF_TO_BLOCK(bp), nlevels - 1,
> type, whichfork, root, ino, tot, nex, blkmapp,
> bm_cursor, isroot, check_dups, &dirty,
> magic);
>
> - ASSERT(dirty == 0 || (dirty && !no_modify));
> -
Here we remove the dirty assert, but don't change the semantics of dirty
(we use badcrc).
Brian
> - if (dirty && !no_modify)
> + if ((dirty || badcrc) && !no_modify)
> libxfs_writebuf(bp, 0);
> else
> libxfs_putbuf(bp);
> @@ -1066,6 +1084,9 @@ scan_freelist(
> do_abort(_("can't read agfl block for ag %d\n"), agno);
> return;
> }
> + if (agflbuf->b_error == EFSBADCRC)
> + do_warn(_("agfl has bad CRC for ag %d\n"), agno);
> +
> freelist = XFS_BUF_TO_AGFL_BNO(mp, agflbuf);
> i = be32_to_cpu(agf->agf_flfirst);
>
> --
> 1.9.0
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-04-15 19:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 8:24 [PATCH 0/9] xfs_db, xfs_repair: improve CRC error detection Dave Chinner
2014-04-15 8:24 ` [PATCH 1/9] db: don't claim unchecked CRCs are correct Dave Chinner
2014-04-21 7:00 ` Christoph Hellwig
2014-04-21 23:13 ` Dave Chinner
2014-04-15 8:24 ` [PATCH 2/9] db: verify buffer on type change Dave Chinner
2014-04-21 7:02 ` Christoph Hellwig
2014-04-21 23:14 ` Dave Chinner
2014-04-15 8:24 ` [PATCH 3/9] repair: ensure prefetched buffers have CRCs validated Dave Chinner
2014-04-15 19:40 ` Brian Foster
2014-04-15 21:46 ` Dave Chinner
2014-04-15 22:06 ` Brian Foster
2014-04-16 0:41 ` Dave Chinner
2014-04-15 8:24 ` [PATCH 4/9] repair: detect and correct CRC errors in directory blocks Dave Chinner
2014-04-21 7:08 ` Christoph Hellwig
2014-04-15 8:24 ` [PATCH 5/9] repair: detect CRC errors in AG headers Dave Chinner
2014-04-15 19:40 ` Brian Foster
2014-04-15 21:52 ` Dave Chinner
2014-04-21 7:11 ` Christoph Hellwig
2014-04-21 23:35 ` Dave Chinner
2014-04-22 6:47 ` Christoph Hellwig
2014-04-22 9:10 ` Dave Chinner
2014-04-22 9:41 ` Christoph Hellwig
2014-04-15 8:24 ` [PATCH 6/9] repair: report AG btree verifier errors Dave Chinner
2014-04-15 19:40 ` Brian Foster [this message]
2014-04-15 21:53 ` Dave Chinner
2014-04-15 8:24 ` [PATCH 7/9] repair: remove more dirv1 leftovers Dave Chinner
2014-04-16 13:23 ` Brian Foster
2014-04-21 7:14 ` Christoph Hellwig
2014-04-21 7:13 ` Christoph Hellwig
2014-04-15 8:25 ` [PATCH 8/9] repair: handle remote sylmlink CRC errors Dave Chinner
2014-04-16 13:23 ` Brian Foster
2014-04-15 8:25 ` [PATCH 9/9] repair: detect and handle attribute tree " Dave Chinner
2014-04-16 13:25 ` Brian Foster
2014-04-21 23:27 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2014-04-24 5:01 [PATCH 0/9 V2] xfs_db, xfs_repair: improve CRC error detection Dave Chinner
2014-04-24 5:01 ` [PATCH 6/9] repair: report AG btree verifier errors Dave Chinner
2014-04-25 5:55 ` Christoph Hellwig
2014-04-28 21:04 [PATCH 0/9 v3] xfs_db, xfs_repair: improve CRC error detection Dave Chinner
2014-04-28 21:04 ` [PATCH 6/9] repair: report AG btree verifier errors 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=20140415194048.GD3470@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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).