From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: fstests <fstests@vger.kernel.org>
Subject: [PATCH] xfs/010,030: filter AG header CRC error warnings
Date: Tue, 28 Jul 2020 19:51:19 -0700 [thread overview]
Message-ID: <20200729025119.GV7600@magnolia> (raw)
From: Darrick J. Wong <darrick.wong@oracle.com>
Filter out the new AG header CRC verification warnings in xfs_repair
since these tests were built before that existed.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
tests/xfs/010 | 7 ++++++-
tests/xfs/030 | 2 ++
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/xfs/010 b/tests/xfs/010
index e220a651..b65dd3ba 100755
--- a/tests/xfs/010
+++ b/tests/xfs/010
@@ -113,7 +113,12 @@ _check_scratch_fs
# nuke the finobt root, repair will have to regenerate from the inobt
_corrupt_finobt_root $SCRATCH_DEV
-_scratch_xfs_repair 2>&1 | _filter_repair_lostblocks
+filter_finobt_repair() {
+ sed -e '/^agi has bad CRC/d' | \
+ _filter_repair_lostblocks
+}
+
+_scratch_xfs_repair 2>&1 | filter_finobt_repair
status=0
exit
diff --git a/tests/xfs/030 b/tests/xfs/030
index efdb6a18..ebe4c92a 100755
--- a/tests/xfs/030
+++ b/tests/xfs/030
@@ -42,6 +42,8 @@ _check_ag()
-e '/^bad agbno AGBNO for finobt/d' \
-e '/^bad agbno AGBNO for rmapbt/d' \
-e '/^bad agbno AGBNO for refcntbt/d' \
+ -e '/^agf has bad CRC/d' \
+ -e '/^agi has bad CRC/d' \
-e '/^Missing reverse-mapping record.*/d' \
-e '/^unknown block state, ag AGNO, block.*/d'
done
next reply other threads:[~2020-07-29 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 2:51 Darrick J. Wong [this message]
2020-07-29 4:49 ` [PATCH] xfs/010,030: filter AG header CRC error warnings Zorro Lang
2020-07-29 14:50 ` Darrick J. Wong
2020-08-26 8:23 ` Yang Xu
2020-08-28 1:33 ` Yang Xu
-- strict thread matches above, loose matches on Subject: below --
2020-07-13 18:49 Darrick J. Wong
2020-07-14 7:13 ` Zorro Lang
2020-07-15 16:57 ` 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=20200729025119.GV7600@magnolia \
--to=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.