Currently, dm-logwrites and common/dmlogwrites don't seem to have any
means to coordinate the event numbers across multiple devices, and the
fstests setup code is sufficiently intense that it doesn't seem like
there's support for multi-disk filesystems. For now, we'll _notrun the
tests when we have external log devices, even though that seems like
something we'd _really_ want to test.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Zorro Lang <zlang@kernel.org>
$UMOUNT_PROG $SCRATCH_LOGDEV 2>/dev/null
}
+# This test requires that an external log device is not in use
+#
+_require_no_logdev()
+{
+ [ "$USE_EXTERNAL" = "yes" ] && [ -n "$SCRATCH_LOGDEV" ] && \
+ _notrun "Test not compatible with external logs, skipped this test"
+}
+
# this test requires loopback device support
#
_require_loop()
_supported_fs generic
_require_test
_require_scratch_nocheck
+_require_no_logdev
_require_log_writes
_require_dm_target thin-pool
_supported_fs generic
_require_test
_require_scratch_reflink
+_require_no_logdev
_require_cp_reflink
_require_log_writes
_require_dm_target thin-pool
# real QA test starts here
_supported_fs generic
_require_scratch_nocheck
+_require_no_logdev
_require_log_writes_dax_mountopt "dax"
_require_dm_target thin-pool
_require_xfs_io_command "mmap" "-S"
# Modify as appropriate.
_supported_fs generic
+_require_no_logdev
_require_command "$KILLALL_PROG" killall
# Use thin device as replay device, which requires $SCRATCH_DEV
_require_scratch_nocheck