This is similar to a previous fix I sent. 1 gig makes us do mixed file block groups for btrfs, so these enospc tests will usually fail because we don't have space for metadata, which is the case for this test. So jack the size up to 1.5gig so that btrfs can do its normal thing and pass the test. Thanks,
Signed-off-by: Josef Bacik <[email protected]> --- tests/generic/256 | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/tests/generic/256 b/tests/generic/256 index 4a53da8..cfe7237 100755 --- a/tests/generic/256 +++ b/tests/generic/256 @@ -165,7 +165,7 @@ _test_full_fs_punch() # Make a small file system to fill umount $SCRATCH_DEV &> /dev/null -_scratch_mkfs_sized $(( 1024 * 1024 * 1024 )) &> /dev/null +_scratch_mkfs_sized $(( 1536 * 1024 * 1024 )) &> /dev/null _scratch_mount # Test must be able to write files with non-root permissions chmod 777 $SCRATCH_MNT -- 1.7.7.6 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
