diff options
author | Darrick J. Wong <darrick.wong@oracle.com> | 2018-07-03 21:51:18 -0700 |
---|---|---|
committer | Eryu Guan <guaneryu@gmail.com> | 2018-07-14 19:42:09 +0800 |
commit | b3cf8b72334fd35ef961869506e5a72ab398bc82 (patch) | |
tree | f99715de4b35dd929f2ece9c7e96f6436cfbc8e9 /tests/xfs/288 | |
parent | 75337edb8cdae7849172e1db986121610782c15e (diff) |
xfs/288: update for v5 filesystem support in xfs_db
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@oracle.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
Diffstat (limited to 'tests/xfs/288')
-rwxr-xr-x | tests/xfs/288 | 8 |
1 files changed, 1 insertions, 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 |