Original reported by Wesley AC: https://github.com/kdave/btrfs-progs/issues/70 Fix it by taking data/meta profile and minimal chunk size into consideration. Also introduce a test case for that. Changelog: v2: Refactor test_minimum_size() to take @min_dev_size directly. Refactor patch already in devel branch. v3: Split test/common modification into separate patch. v4: Further split run_mustfail_stdout() and prepare_test_dev() modification into separate patch. Include the real mkfs fix into patchset, to prevent possible test failure. Use suggestion from David to use run_check_mount_test_dev() and run_check_umount_test_dev(). Add "-b $good_size" to mkfs command line, so we can see the size in test result, to help further debugging. Qu Wenruo (4): btrfs-progs: mkfs: Enhance minimal device size calculation to fix mkfs failure on small file btrfs-progs: test/common: Introduce run_mustfail_stdout btrfs-progs: test/common: Enhance prepare_test_dev to reset device size btrfs-progs: test/mkfs: Test if the minimal device size is valid mkfs/common.c | 68 ++++++++++++++++++++++++++++---- mkfs/common.h | 4 +- mkfs/main.c | 3 +- tests/common | 58 ++++++++++++++++++++++++++- tests/mkfs-tests/010-small-image/test.sh | 49 +++++++++++++++++++++++ 5 files changed, 171 insertions(+), 11 deletions(-) create mode 100755 tests/mkfs-tests/010-small-image/test.sh -- 2.14.3 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
