From: Brian Foster <bfoster@redhat.com>
To: fstests@vger.kernel.org
Cc: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfstests: xfsprogs logformat tests
Date: Wed, 25 Nov 2015 15:19:48 -0500 [thread overview]
Message-ID: <1448482790-44469-1-git-send-email-bfoster@redhat.com> (raw)
Hi all,
Here are a couple prospective tests that use the recently posted xfs_db
logformat command:
http://oss.sgi.com/pipermail/xfs/2015-November/045139.html
Note that these should not be merged until xfs_db logformat support is
fully reviewed and merged into xfsprogs. Also note that the test numbers
are arbitrarily high and should be renumbered.
Patch 1 adds a test that uses xfs_logprint to verify that logformat
formats the log correctly with various stripe unit alignments. Patch 2
uses the logformat command to test invalid metadata LSN detection and
recovery. Thoughts, reviews, flames appreciated.
Brian
Brian Foster (2):
tests/xfs: test xfsprogs log formatting infrastructure
tests/xfs: verify invalid metadata LSN detection
common/rc | 14 +++++++++
tests/xfs/376 | 71 +++++++++++++++++++++++++++++++++++++++++++
tests/xfs/376.out | 6 ++++
tests/xfs/377 | 90 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/377.out | 3 ++
tests/xfs/group | 2 ++
6 files changed, 186 insertions(+)
create mode 100755 tests/xfs/376
create mode 100644 tests/xfs/376.out
create mode 100755 tests/xfs/377
create mode 100644 tests/xfs/377.out
--
2.1.0
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-11-25 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 20:19 Brian Foster [this message]
2015-11-25 20:19 ` [PATCH 1/2] tests/xfs: test xfsprogs log formatting infrastructure Brian Foster
2015-11-25 20:19 ` [PATCH 2/2] tests/xfs: verify invalid metadata LSN detection 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=1448482790-44469-1-git-send-email-bfoster@redhat.com \
--to=bfoster@redhat.com \
--cc=fstests@vger.kernel.org \
--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