2020-06-16 06:32:30 +00:00
|
|
|
#!/bin/bash
|
|
|
|
|
# Regression test for mkfs.btrfs --rootdir with DUP data profile and rootdir
|
|
|
|
|
# size near the limit of the device.
|
|
|
|
|
#
|
|
|
|
|
# There is a bug that makes mkfs.btrfs always to create unnecessary SINGLE
|
|
|
|
|
# chunks, which eats up a lot of space and leads to unexpected ENOSPC bugs.
|
|
|
|
|
|
2023-04-19 15:08:41 +00:00
|
|
|
source "$TEST_TOP/common" || exit
|
2020-06-16 06:32:30 +00:00
|
|
|
|
|
|
|
|
check_prereq mkfs.btrfs
|
2023-04-13 18:40:23 +00:00
|
|
|
|
2020-06-16 06:32:30 +00:00
|
|
|
prepare_test_dev
|
|
|
|
|
|
2021-10-11 13:56:58 +00:00
|
|
|
tmp=$(_mktemp_dir mkfs-rootdir)
|
2020-06-16 06:32:30 +00:00
|
|
|
|
|
|
|
|
fallocate -l 128M $tmp/large_file
|
|
|
|
|
|
|
|
|
|
# We should be able to create the fs with size limit to 2 * (128 + 32 + 8)
|
|
|
|
|
# which is 336M. Here we round it up to 350M.
|
|
|
|
|
run_check "$TOP/mkfs.btrfs" -f --rootdir "$tmp" -d dup -b 350M "$TEST_DEV"
|
|
|
|
|
run_check "$TOP/btrfs" check "$TEST_DEV"
|
|
|
|
|
|
|
|
|
|
rm -rf -- "$tmp"
|
