RepoMirrors
/
btrfs-progs
mirror of https://github.com/kdave/btrfs-progs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
btrfs-progs/tests/misc-tests/058-replace-start-enqueue/test.sh

44 lines
1.4 KiB
Bash
Raw Normal View History

btrfs-progs: tests: check if enqueued replace over replace waits Signed-off-by: David Sterba <dsterba@suse.com>
2023-07-14 23:31:35 +00:00
#!/bin/bash
# Check that an enqueued replace over another replace will wait
source "$TEST_TOP/common" || exit
check_prereq mkfs.btrfs
check_prereq btrfs
setup_root_helper
setup_loopdevs 6
prepare_loopdevs
TEST_DEV=${loopdevs[1]}
REPLACE1=${loopdevs[6]}
REPLACE2=${loopdevs[5]}
# Use striped profile so all devices are at least partially filled
run_check $SUDO_HELPER "$TOP/mkfs.btrfs" -f -d raid0 -m raid0 "${loopdevs[@]}"
run_check_mount_test_dev
# Remove the devices and then use them for replace
run_check $SUDO_HELPER "$TOP/btrfs" device remove "$REPLACE1" "$TEST_MNT"
run_check $SUDO_HELPER "$TOP/btrfs" device remove "$REPLACE2" "$TEST_MNT"
btrfs-progs: tests: misc/058: reduce the space requirement and speed up the test [BUG] When I was testing misc/058, the fs still has around 7GiB free space, but during that test case, btrfs kernel module reports write failures and even git commands failed inside that fs. And obviously the test case failed. [CAUSE] It turns out that, the test case itself would require 6GiB (4 data disks) + 1.5GiB x 2 (the two replace target), thus it requires 9 GiB free space. And obviously my partition is not that large and failed. [FIX] In fact, we really don't need that much space at all. The test verifies that two consecutive replace operations can be started and enqueued, the sleep of 1 second is not strictly necessary as the first command should start the replace right away. Reviewed-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
2023-08-08 06:55:21 +00:00
for i in `seq 16`; do
btrfs-progs: tests: check if enqueued replace over replace waits Signed-off-by: David Sterba <dsterba@suse.com>
2023-07-14 23:31:35 +00:00
run_check $SUDO_HELPER dd if=/dev/zero of="$TEST_MNT/file$i" bs=1M count=128 status=noxfer
done
# Sync so replace start does not block in unwritten IO
run_check "$TOP/btrfs" filesystem sync "$TEST_MNT"
run_check "$TOP/btrfs" filesystem usage -T "$TEST_MNT"
btrfs-progs: tests: misc/058: reduce the space requirement and speed up the test [BUG] When I was testing misc/058, the fs still has around 7GiB free space, but during that test case, btrfs kernel module reports write failures and even git commands failed inside that fs. And obviously the test case failed. [CAUSE] It turns out that, the test case itself would require 6GiB (4 data disks) + 1.5GiB x 2 (the two replace target), thus it requires 9 GiB free space. And obviously my partition is not that large and failed. [FIX] In fact, we really don't need that much space at all. The test verifies that two consecutive replace operations can be started and enqueued, the sleep of 1 second is not strictly necessary as the first command should start the replace right away. Reviewed-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
2023-08-08 06:55:21 +00:00
# Go background, should not be that fast.
btrfs-progs: tests: check if enqueued replace over replace waits Signed-off-by: David Sterba <dsterba@suse.com>
2023-07-14 23:31:35 +00:00
run_check $SUDO_HELPER "$TOP/btrfs" replace start 2 "$REPLACE1" "$TEST_MNT"
# No background, should wait
run_check $SUDO_HELPER "$TOP/btrfs" replace start --enqueue 3 "$REPLACE2" "$TEST_MNT"
run_check $SUDO_HELPER "$TOP/btrfs" replace status "$TEST_MNT"
run_check "$TOP/btrfs" filesystem sync "$TEST_MNT"
run_check "$TOP/btrfs" filesystem usage -T "$TEST_MNT"
run_check $SUDO_HELPER "$TOP/btrfs" replace status "$TEST_MNT"
run_check_umount_test_dev
cleanup_loopdevs