From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 5/9] repair: detect CRC errors in AG headers
Date: Fri, 2 May 2014 09:27:20 +1000 [thread overview]
Message-ID: <20140501232720.GD22353@dastard> (raw)
In-Reply-To: <20140429140619.GC59046@bfoster.bfoster>
On Tue, Apr 29, 2014 at 10:06:19AM -0400, Brian Foster wrote:
> On Tue, Apr 29, 2014 at 07:04:55AM +1000, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> >
> > repair doesn't currently detect verifier errors in AG header
> > blocks - apart from the primary superblock they are not detected.
> > They are, fortunately, corrected in the important cases (AGF, AGI
> > and AGFL) because these structures are rebuilt in phase 5, but if
> > you run xfs_repair in checking mode it won't report them as bad.
> >
> > Signed-off-by: Dave Chinner <dchinner@redhat.com>
.....
> > @@ -1312,21 +1302,34 @@ scan_ag(
> > validate_agi(agi, agno, agcnts);
> >
> > ASSERT(agi_dirty == 0 || (agi_dirty && !no_modify));
> > + ASSERT(agf_dirty == 0 || (agf_dirty && !no_modify));
> > + ASSERT(sb_dirty == 0 || (sb_dirty && !no_modify));
> > +
> > + /*
> > + * Only pay attention to CRC/verifier errors if we can correct them.
> > + * While there, ensure that we corrected a corruption error if the
> > + * verifier detected one.
> > + */
> > + if (!no_modify) {
> > + ASSERT(agi_dirty || agibuf->b_error != EFSCORRUPTED);
> > + ASSERT(agf_dirty || agfbuf->b_error != EFSCORRUPTED);
> > + ASSERT(sb_dirty || sbbuf->b_error != EFSCORRUPTED);
> > +
> > + agi_dirty += (agibuf->b_error == EFSBADCRC);
> > + agf_dirty += (agfbuf->b_error == EFSBADCRC);
> > + sb_dirty += (sbbuf->b_error == EFSBADCRC);
> > + }
>
> So we'll detect and correct the CRC error in normal mode, but no longer
> issue the preceding warnings ("would reset bad ...") for CRC errors in
> no_modify mode. Is that desired?
It will still throw a bad CRC error, so the user is still told that
there is a problem.
> I ask because it looks like a departure from previous versions.
> Otherwise, the code looks fine to me.
Slightly, but I don't think it makes much difference...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-01 23:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 1/9] db: don't claim unchecked CRCs are correct Dave Chinner
2014-04-28 21:04 ` [PATCH 2/9] db: verify buffer on type change Dave Chinner
2014-04-28 21:04 ` [PATCH 3/9] repair: ensure prefetched buffers have CRCs validated Dave Chinner
2014-04-29 14:05 ` Brian Foster
2014-04-29 18:15 ` Christoph Hellwig
2014-04-28 21:04 ` [PATCH 4/9] repair: detect and correct CRC errors in directory blocks Dave Chinner
2014-04-28 21:04 ` [PATCH 5/9] repair: detect CRC errors in AG headers Dave Chinner
2014-04-29 14:06 ` Brian Foster
2014-05-01 23:27 ` Dave Chinner [this message]
2014-04-29 18:16 ` Christoph Hellwig
2014-04-28 21:04 ` [PATCH 6/9] repair: report AG btree verifier errors Dave Chinner
2014-04-28 21:04 ` [PATCH 7/9] repair: remove more dirv1 leftovers Dave Chinner
2014-04-28 21:04 ` [PATCH 8/9] repair: handle remote symlink CRC errors Dave Chinner
2014-04-29 14:06 ` Brian Foster
2014-04-29 18:17 ` Christoph Hellwig
2014-04-28 21:04 ` [PATCH 9/9] repair: detect and handle attribute tree " Dave Chinner
2014-04-29 14:06 ` Brian Foster
2014-04-30 3:55 ` Dave Chinner
2014-04-29 18:18 ` Christoph Hellwig
-- 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 5/9] repair: detect CRC errors in AG headers Dave Chinner
2014-04-25 5:55 ` Christoph Hellwig
2014-04-15 8:24 [PATCH 0/9] xfs_db, xfs_repair: improve CRC error detection Dave Chinner
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
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=20140501232720.GD22353@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.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).