So this test can support both block device and loop device simply. Signed-off-by: Zhao Lei <zhaolei@xxxxxxxxxxxxxx> --- tests/misc-tests/007-subvolume-sync/test.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/misc-tests/007-subvolume-sync/test.sh b/tests/misc-tests/007-subvolume-sync/test.sh index d4019f4..1eea098 100755 --- a/tests/misc-tests/007-subvolume-sync/test.sh +++ b/tests/misc-tests/007-subvolume-sync/test.sh @@ -13,7 +13,7 @@ setup_root_helper prepare_test_dev run_check $SUDO_HELPER $TOP/mkfs.btrfs -f "$TEST_DEV" -run_check $SUDO_HELPER mount "$TEST_DEV" "$TEST_MNT" +run_check $SUDO_HELPER mount_test_dev # to check following thing in both 1 and multiple subvolume case: # 1: is subvolume sync loop indefinetelly @@ -29,4 +29,4 @@ run_check $SUDO_HELPER $TOP/btrfs subvolume create "$TEST_MNT"/mysubvol run_check $SUDO_HELPER $TOP/btrfs subvolume delete "$TEST_MNT"/mysubvol run_check $SUDO_HELPER $TOP/btrfs subvolume sync "$TEST_MNT" -run_check $SUDO_HELPER umount $TEST_MNT +run_check $SUDO_HELPER umount_test_dev -- 1.8.5.1 -- 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
