On Sun, Aug 30, 2015 at 08:14:48PM +0530, Chandan Rajendra wrote: > When creating small Btrfs filesystem instances (i.e. filesystem size <= 1GiB), > mkfs.btrfs can fail if "data block size" does not match "metadata block > size". In such cases this commit aborts the test instead of letting it to > continue and report misleading results.
NACK. Running the test, even with the wrong mkfs parameters, is more valuable to us than not running the test at all. This has been explained several times in the past 18 months when similar patches have been posted. What you need to do is prevent mkfs from failing in your new corner case on small filesystems, or fail the test in the the filesystem specific mkfs routine. e.g. Filesystems like xfs have custom functions (i.e. _scratch_mkfs_xfs) that prevent mkfs from failing in weird corner cases or when conflicting options are given (e.g. test option conflict with MKFS_OPTIONS given on the CLI). Or, you can make the btrfs mkfs command in _scratch_mkfs_sized() specially handle this specific btrfs configuration correctly, and if it can't then it should fail there. Cheers, Dave. -- Dave Chinner [email protected] -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
