public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: fstests@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH 2/6] ext4/044: skip test if the file system does not have a journal
Date: Tue, 28 Jun 2022 14:25:41 -0400	[thread overview]
Message-ID: <20220628182545.1834145-3-tytso@mit.edu> (raw)
In-Reply-To: <20220628182545.1834145-1-tytso@mit.edu>

This test mounts the file system using "mount -t ext3"; if the file
system config creates the file system without the jbd2 journal, the
"mount -t ext3" will fail.  So skip this test in that case.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
 tests/ext4/044 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/ext4/044 b/tests/ext4/044
index 46e44053..158e2ac5 100755
--- a/tests/ext4/044
+++ b/tests/ext4/044
@@ -16,6 +16,7 @@ _begin_fstest auto quick
 _supported_fs ext4
 _require_scratch
 _require_test_program "t_get_file_time"
+_require_metadata_journaling
 
 echo "Silence is golden"
 
-- 
2.31.0


  parent reply	other threads:[~2022-06-28 18:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 18:25 [PATCH -v2 0/6] Miscellaneous ext4 test fix ups Theodore Ts'o
2022-06-28 18:25 ` [PATCH 1/6] ext4/050: support indirect as well as extent mapped journals Theodore Ts'o
2022-06-28 18:25 ` Theodore Ts'o [this message]
2022-06-28 18:25 ` [PATCH 3/6] ext4/045: _require_dumpe2fs doesn't take any arguments so remove them Theodore Ts'o
2022-06-28 18:25 ` [PATCH 4/6] ext4/054: skip test if the dax mount option is enabled Theodore Ts'o
2022-06-28 18:25 ` [PATCH 5/6] ext4/055: skip test if dax mount option is used Theodore Ts'o
2022-06-28 18:25 ` [PATCH 6/6] ext4: create file systems with the enrypt feature if necessary Theodore Ts'o
2022-06-29  5:16   ` Eric Biggers
2022-06-29 12:28     ` Theodore Ts'o
2022-06-29  8:58   ` Zorro Lang

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=20220628182545.1834145-3-tytso@mit.edu \
    --to=tytso@mit.edu \
    --cc=fstests@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