On 10.01.2018 06:56, Qu Wenruo wrote:
> Signed-off-by: Qu Wenruo <wqu@xxxxxxxx>
Reviewed-by: Nikolay Borisov <nborisov@xxxxxxxx>
> ---
> .../mkfs-tests/010-reserved-1M-for-single/test.sh | 37 ++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
> create mode 100755 tests/mkfs-tests/010-reserved-1M-for-single/test.sh
>
> diff --git a/tests/mkfs-tests/010-reserved-1M-for-single/test.sh b/tests/mkfs-tests/010-reserved-1M-for-single/test.sh
> new file mode 100755
> index 000000000000..1a4936eaf72e
> --- /dev/null
> +++ b/tests/mkfs-tests/010-reserved-1M-for-single/test.sh
> @@ -0,0 +1,37 @@
> +#!/bin/bash
> +# Test if "-m single" or "-M" can cause dev extent to use reserved 1M range
> +#
> +# Other profiles will cause mkfs.btrfs to allocate new meta/sys chunks
> +# using btrfs_alloc_chunk() which won't use 0~1M range, so other profiles
> +# are safe.
> +
> +source "$TOP/tests/common"
> +
> +check_prereq mkfs.btrfs
> +check_prereq btrfs
> +
> +prepare_test_dev
> +
> +do_one_test ()
> +{
> + run_check "$TOP/mkfs.btrfs" -f $@ "$TEST_DEV"
> +
> + # Use dev-extent tree to find first device extent
> + first_dev_extent=$(run_check_stdout "$TOP/btrfs" inspect-internal \
> + dump-tree -t device "$TEST_DEV" | \
> + grep -oP '(?<=DEV_EXTENT )[[:digit:]]*' | head -n1)
> +
> + if [ -z $first_dev_extent ]; then
> + _fail "Failed to get first device extent"
> + fi
> +
> + echo "First dev extent starts at $first_dev_extent" >> "$RESULTS"
> + echo "Reserved range is [0, $(( 1024 * 1024)))" >> "$RESULTS"
> + # First device extent should not start below 1M
> + if [ $first_dev_extent -lt $(( 1024 * 1024 )) ]; then
> + _fail "First device extent occupies reserved 0~1M range"
> + fi
> +}
> +
> +do_one_test "-M"
> +do_one_test "-m single"
>
--
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
