From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 1/5] xfs/030: filter out extra repair noise for finobt enabled fs'
Date: Fri, 2 May 2014 13:13:58 -0400 [thread overview]
Message-ID: <1399050842-19633-2-git-send-email-bfoster@redhat.com> (raw)
In-Reply-To: <1399050842-19633-1-git-send-email-bfoster@redhat.com>
xfs/030 nukes various on-disk data structures to test for repair. This
can result in extra output when testing finobt enabled filesystems. For
example, xfs_repair detects an invalid free inode btree root block when
the agi is zeroed.
Filter this output directly in xfs/030 such that the test passes for
finobt and non-finobt filesystems.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
tests/xfs/030 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/xfs/030 b/tests/xfs/030
index af03166..a43455f 100755
--- a/tests/xfs/030
+++ b/tests/xfs/030
@@ -56,7 +56,8 @@ _check_ag()
do
echo "Corrupting $structure - setting bits to $1"
_check_repair $1 "$structure" |
- sed -e '/^error following ag 0 unlinked list$/d'
+ sed -e '/^error following ag 0 unlinked list$/d' \
+ -e '/^bad agbno AGBNO for finobt/d'
done
}
--
1.8.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-02 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 17:13 [PATCH 0/5] xfstests: fixes for the free inode btree Brian Foster
2014-05-02 17:13 ` Brian Foster [this message]
2014-05-02 17:13 ` [PATCH 2/5] xfstests: add _require_xfs_[mkfs_]finobt() checks for finobt tests Brian Foster
2014-05-02 17:14 ` [PATCH 3/5] xfstests: filter agno/ino repair output for finobt Brian Foster
2014-05-02 17:14 ` [PATCH 4/5] xfs/010: test repair for finobt corruption Brian Foster
2014-05-02 17:14 ` [PATCH 5/5] xfs/013: stress the free inode btree Brian Foster
2014-05-02 23:48 ` [PATCH 0/5] xfstests: fixes for " Dave Chinner
2014-05-05 11:34 ` Brian Foster
2014-05-21 0:20 ` Dave Chinner
2014-05-21 11:31 ` Brian Foster
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=1399050842-19633-2-git-send-email-bfoster@redhat.com \
--to=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).