apfs/apfstests
0
0
Fork 0
mirror of https://github.com/linux-apfs/apfstests.git synced 2026-05-01 15:01:44 -07:00
Code Issues Packages Projects Releases Wiki Activity

xfs/187: fix ftype brokenness

Browse Source 
This test requires XFS_SB_VERSION_MOREBITSBIT to be zero.  ftype (which
is now enabled by default) causes this to be set, so detect it in mkfs
and disable it.

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>
This commit is contained in:
Darrick J. Wong
2018-04-11 09:08:09 -07:00
committed by Eryu Guan
parent 858c39281e
commit fdf6d4bc86
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/xfs/187
+9 -2
View File
@@ -70,8 +70,15 @@ export MOUNT_OPTIONS=""
# lazysb, attr2 and other feature bits are held in features2 and will require
# morebitsbit on So test with lazysb and without it to see if the morebitsbit is
# okay etc. If the mkfs defaults change, these need to change as well.
export MKFS_NO_LAZY="-m crc=0 -l lazy-count=0 -i projid32bit=0"
export MKFS_LAZY="-m crc=0 -l lazy-count=1 -i projid32bit=0"
MKFS_NO_LAZY="-m crc=0 -l lazy-count=0 -i projid32bit=0"
MKFS_LAZY="-m crc=0 -l lazy-count=1 -i projid32bit=0"
# ftype is also stored in features2, so we have to detect its presence in
# mkfs and disable it here too.
if _scratch_mkfs --help 2>&1 | grep -q "ftype="; then
MKFS_NO_LAZY="$MKFS_NO_LAZY -n ftype=0"
MKFS_LAZY="$MKFS_LAZY -n ftype=0"
fi
# Make sure that when we think we are testing with morebits off
# that we really are.