From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: eguan@redhat.com, darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 3/3] xfs/030: ignore lost rmapbt blocks
Date: Sat, 28 Jan 2017 09:38:25 -0800 [thread overview]
Message-ID: <148562510529.30594.2372809333277654802.stgit@birch.djwong.org> (raw)
In-Reply-To: <148562509264.30594.7506967863745489318.stgit@birch.djwong.org>
From: Darrick J. Wong <darrick.wong@oracle.com>
When we destroy the AG0 headers, we also lose track of the rmapbt
blocks, which causes xfs_repair to complain about their unconnectedness.
Filter out the error message from the output.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
tests/xfs/030 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/xfs/030 b/tests/xfs/030
index 5c99d9e..15f41ed 100755
--- a/tests/xfs/030
+++ b/tests/xfs/030
@@ -60,7 +60,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 '/^Missing reverse-mapping record.*/d'
+ -e '/^Missing reverse-mapping record.*/d' \
+ -e '/^unknown block state, ag 0, block.*/d'
done
}
next prev parent reply other threads:[~2017-01-28 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 17:38 [PATCH 1/3] xfs/263: don't hardcode inode numbers in output Darrick J. Wong
2017-01-28 17:38 ` [PATCH 2/3] xfs/299: don't chmod the underlying mountpoints prior to mounting Darrick J. Wong
2017-01-28 17:38 ` Darrick J. Wong [this message]
2017-01-28 18:10 ` [PATCH 1/3] xfs/263: don't hardcode inode numbers in output Eric Sandeen
2017-01-28 20:30 ` Darrick J. Wong
2017-02-03 6:42 ` Eryu Guan
2017-02-03 17:46 ` 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=148562510529.30594.2372809333277654802.stgit@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--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).