From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: latest xfstests-bld and nojournal test failures
Date: Tue, 16 Aug 2016 17:45:19 -0400 [thread overview]
Message-ID: <20160816214519.GA18888@localhost.localdomain> (raw)
FYI for those running the latest version of the test appliance:
Commit 5e574181f3bf ("test appliance - automate selection of
test/scratch devices") deleted the ^has_journal option from the
MKFS_OPTIONS string in the configuration file for the nojournal test
case. This leads to failures for generic/034 and 18 other tests in the
nojournal test case; all of them were prevented from running in the
previous version of the test appliance by the xfstest function
_require_metadata_journaling().
That function determines whether a test file system supports metadata
journaling by using dumpe2fs to see whether the test or scratch file
system contains a journal. Use of the noload mount option as
specified by EXT_MOUNT_OPTIONS doesn't affect that determination.
It looks like we'll want to add code to _require_metadata_journaling to
check for use of the noload mount option as well as presence/absence of a
journal.
Eric
reply other threads:[~2016-08-16 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160816214519.GA18888@localhost.localdomain \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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