From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> The xfs_db 'write -d' command has supported v5 filesystems for a few releases now, and there's nothing about this test that require v4, so let the test run with v5 if the user so specifies. Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> --- tests/xfs/288 | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/tests/xfs/288 b/tests/xfs/288 index e7a08a5d..bccdb6fc 100755 --- a/tests/xfs/288 +++ b/tests/xfs/288 @@ -36,14 +36,8 @@ _supported_os Linux _require_scratch _require_attrs -# Due to xfs_db's write -d option is still not stable, and there's no -# plan to support attr3. So only run this case on V4 XFS. -# Please update this if xfs_db get enough improvement in one day. -if [ -z "$XFS_MKFS_HAS_NO_META_SUPPORT" ]; then - mkfs_opts="-m crc=0" -fi # get block size ($dbsize) from the mkfs output -_scratch_mkfs_xfs $mkfs_opts 2>/dev/null | _filter_mkfs 2>$tmp.mkfs >/dev/null +_scratch_mkfs_xfs 2>/dev/null | _filter_mkfs 2>$tmp.mkfs >/dev/null . $tmp.mkfs _scratch_mount -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
