A large number of xfs-specific tests rely on specific behaviors of the
data device allocator, such as fragmenting free space, carefully curated
inode and free space counts, or features like filestreams that only
exist on the data device.
These tests fail horribly if the test runner specified rtinherit=1 on
the mkfs command line, so skip them all.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Zorro Lang <zlang@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
_supported_os Linux
_require_scratch
+_require_no_rtinherit
_check_filestreams_support || _notrun "filestreams not available"
_supported_os Linux
_require_scratch
+_require_no_rtinherit
_check_filestreams_support || _notrun "filestreams not available"
_supported_os Linux
_require_scratch
+_require_no_rtinherit
_check_filestreams_support || _notrun "filestreams not available"
_supported_os Linux
_require_scratch
+_require_no_rtinherit
_check_filestreams_support || _notrun "filestreams not available"
# single AG will cause xfs_repair to fail checks.
_require_scratch_nocheck
+_require_no_rtinherit
rm -f $seqres.full
_supported_os Linux
_require_scratch_nocheck # check complains about single AG fs
+_require_no_rtinherit
_require_xfs_io_command "fpunch"
_require_command $UUIDGEN_PROG uuidgen
_require_scratch
_require_error_injection
_require_xfs_io_error_injection "rmap_finish_one"
+_require_no_rtinherit
rm -f $seqres.full
_require_test_program "punch-alternating"
_require_xfs_io_command "falloc"
_require_xfs_db_write_array
+_require_no_rtinherit
# This is only a v5 filesystem problem
_require_scratch_xfs_crc