From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 3/5] xfstests: filter agno/ino repair output for finobt
Date: Fri, 2 May 2014 13:14:00 -0400 [thread overview]
Message-ID: <1399050842-19633-4-git-send-email-bfoster@redhat.com> (raw)
In-Reply-To: <1399050842-19633-1-git-send-email-bfoster@redhat.com>
finobt enabled filesystems can generate new repair output. Update
_filter_repair() to ensure specific AG and inode numbers are filtered
from test output.
Signed-off-by: Brian Foster <bfoster@redhat.com>
---
common/repair | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/repair b/common/repair
index 3e73c1d..46ca9e0 100644
--- a/common/repair
+++ b/common/repair
@@ -83,6 +83,8 @@ s/\s+- \d+:\d\d:\d\d:.*\n//g;
/^Metadata corruption detected/ && next;
/^Metadata CRC error detected/ && next;
/^agfl has bad CRC/ && next;
+# finobt enabled filesystem output
+s/(inode chunk) (\d+)\/(\d+)/AGNO\/INO/;
print;'
}
--
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 ` [PATCH 1/5] xfs/030: filter out extra repair noise for finobt enabled fs' Brian Foster
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 ` Brian Foster [this message]
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-4-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).