xfstests: fix up features2 tests for lazy-count=1
PATCH 1/1 xfstests: fix up features2 tests for lazy-count=1
A few more tests are unhappy with a lazy-count=1 change; specify lazy-count=0 in them for these tests.
Signed-off-by Eric Sandeen <[email protected]>
---
186 +1 -1
@@ -135,7 +135,7 @@ _supported_os Linux _require_scratch rm -f $seq.full -_scratch_mkfs -i attr=2,size=512 >/dev/null 2>&1 +_scratch_mkfs -i attr=2,size=512 -l lazy-count=0 >/dev/null 2>&1 # set inum to root dir ino # we'll add in dirents and EAs into the root directory
187 +1 -1
@@ -54,7 +54,7 @@ export MOUNT_OPTIONS="" # Make sure that when we think we are testing with morebits off # that we really are. # Trying to future-proof in case mkfs defaults change. -_scratch_mkfs -i attr=1 >/dev/null 2>&1 +_scratch_mkfs -i attr=1 -l lazy-count=0 >/dev/null 2>&1 $XFS_DB_PROG -c version $SCRATCH_DEV 2>&1 >$tmp.db if grep -i morebits $tmp.db then
199 +1 -1
@@ -35,7 +35,7 @@ _supported_os Linux _require_scratch -_scratch_mkfs_xfs >/dev/null 2>&1 +_scratch_mkfs_xfs -l lazy-count=0>/dev/null 2>&1 # # Print the current flags. Just a dummy so that the test breaks
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 2 lines · Eric Sandeen
A few more tests are unhappy with a lazy-count=1 change; specify lazy-count=0 in them for these tests.
Again I'd prefer them to either deal with both cases and if that's not feasible test the lazy-count=1 case.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs