[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140129204502.GC2165@wallace>
Date: Wed, 29 Jan 2014 15:45:02 -0500
From: Eric Whitney <enwlinux@...il.com>
To: xfs@....sgi.com
Cc: linux-ext4@...r.kernel.org
Subject: [PATCH] xfstests: avoid ext4/306 failures caused by incompatible
mount options
ext4/306 will fail when mounting the ext3 file system it creates if an
ext3-incompatible mount option is applied by _scratch_mount. This can
happen if EXT_MOUNT_OPTIONS is defined appropriately in the test
environment. For example, the block_validity option is commonly used
to enhance ext4 testing, and it is not supported by ext3. Fix this by
not including any mount options defined by the test environment.
Signed-off-by: Eric Whitney <enwlinux@...il.com>
---
tests/ext4/306 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/ext4/306 b/tests/ext4/306
index 398c4c0..e59c8ed 100755
--- a/tests/ext4/306
+++ b/tests/ext4/306
@@ -52,9 +52,10 @@ grep -q ext3 /proc/filesystems || _notrun "This test requires ext3 support"
rm -f $seqres.full
-# Make a small ext3 fs, (extents disabled) & mount it
+# Make a small ext3 fs, (extents disabled)
yes | mkfs.ext3 $SCRATCH_DEV 512m >> $seqres.full 2>&1
-_scratch_mount -t ext3 || _fail "couldn't mount fs as ext3"
+# Mount it without _scratch_mount to avoid any ext3-incompatible mount options
+_mount -t ext3 $SCRATCH_DEV $SCRATCH_MNT || _fail "couldn't mount fs as ext3"
# Create a small non-extent-based file
echo "Create 1m testfile1"
$XFS_IO_PROG -f $SCRATCH_MNT/testfile1 -c "pwrite 0 1m" | _filter_xfs_io
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists