From 0509c05ae6bd7461964d3e483246aa07a63ee6d0 Mon Sep 17 00:00:00 2001 From: Josh Soref Date: Mon, 26 Nov 2018 17:53:43 +0100 Subject: btrfs-progs: tests: fix typos in test comments Generated by https://github.com/jsoref/spelling Issue: #154 Author: Josh Soref Signed-off-by: David Sterba --- tests/cli-tests/007-check-force/test.sh | 2 +- tests/common | 2 +- tests/fsck-tests/031-metadatadump-check-data-csum/test.sh | 4 ++-- tests/fsck-tests/036-rescan-not-kicked-in/test.sh | 2 +- tests/misc-tests/006-image-on-missing-device/test.sh | 2 +- tests/misc-tests/029-send-p-different-mountpoints/test.sh | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/tests/cli-tests/007-check-force/test.sh b/tests/cli-tests/007-check-force/test.sh index 597f2d60..deee96c8 100755 --- a/tests/cli-tests/007-check-force/test.sh +++ b/tests/cli-tests/007-check-force/test.sh @@ -10,7 +10,7 @@ check_prereq btrfs setup_root_helper # we need to use a real block device, because the check opens the device in -# exclusive mode, that unfortunatelly behaves differently for direct file +# exclusive mode, that unfortunately behaves differently for direct file # access and for the real /dev/loop0 device setup_loopdevs 1 prepare_loopdevs diff --git a/tests/common b/tests/common index 7e4e09df..1575ae38 100644 --- a/tests/common +++ b/tests/common @@ -171,7 +171,7 @@ run_check_stdout() } # same as run_check but does not fail the test if it's handled gracefully by -# the tool, unexpected failure like segfault or abor will exit forcibly +# the tool, unexpected failure like segfault or abort will exit forcibly # output is logged run_mayfail() { diff --git a/tests/fsck-tests/031-metadatadump-check-data-csum/test.sh b/tests/fsck-tests/031-metadatadump-check-data-csum/test.sh index e9b2d5c6..7f3872e6 100755 --- a/tests/fsck-tests/031-metadatadump-check-data-csum/test.sh +++ b/tests/fsck-tests/031-metadatadump-check-data-csum/test.sh @@ -1,5 +1,5 @@ #!/bin/bash -# To check if "btrfs check" can detect metadata dump (restored by btrfs-iamge) +# To check if "btrfs check" can detect metadata dump (restored by btrfs-image) # and ignore --check-data-csum option source "$TEST_TOP/common" @@ -21,7 +21,7 @@ chmod a+w restored_image run_check $SUDO_HELPER "$TOP/btrfs-image" "$TEST_DEV" "restored_image" # use prepare_test_dev() to wipe all existing data on $TEST_DEV -# so there is no way that restored image could have mathcing data csum +# so there is no way that restored image could have matching data csum prepare_test_dev run_check $SUDO_HELPER "$TOP/btrfs-image" -r "restored_image" "$TEST_DEV" diff --git a/tests/fsck-tests/036-rescan-not-kicked-in/test.sh b/tests/fsck-tests/036-rescan-not-kicked-in/test.sh index 82fa978e..eafd599d 100755 --- a/tests/fsck-tests/036-rescan-not-kicked-in/test.sh +++ b/tests/fsck-tests/036-rescan-not-kicked-in/test.sh @@ -4,7 +4,7 @@ # low probability. # # This test case verifies a special case when 'btrfs check' does not report -# qgroup accounting differece as an error, thus no false alert for btrfs/166. +# qgroup accounting difference as an error, thus no false alert for btrfs/166. source "$TEST_TOP/common" diff --git a/tests/misc-tests/006-image-on-missing-device/test.sh b/tests/misc-tests/006-image-on-missing-device/test.sh index 2b222340..8c81e6fb 100755 --- a/tests/misc-tests/006-image-on-missing-device/test.sh +++ b/tests/misc-tests/006-image-on-missing-device/test.sh @@ -1,7 +1,7 @@ #!/bin/bash # test btrfs-image with a missing device (uses loop devices) # -# - btrfs-image must not loop indefinetelly +# - btrfs-image must not loop indefinitely # - btrfs-image will expectedly fail to produce the dump source "$TEST_TOP/common" diff --git a/tests/misc-tests/029-send-p-different-mountpoints/test.sh b/tests/misc-tests/029-send-p-different-mountpoints/test.sh index 90465e1d..a59a585e 100755 --- a/tests/misc-tests/029-send-p-different-mountpoints/test.sh +++ b/tests/misc-tests/029-send-p-different-mountpoints/test.sh @@ -10,7 +10,7 @@ check_prereq mkfs.btrfs setup_root_helper prepare_test_dev -# we need two mount points, cannot nest the subvoolume under TEST_MNT +# we need two mount points, cannot nest the subvolume under TEST_MNT SUBVOL_MNT="$TEST_MNT/subvol" TOPLEVEL_MNT="$TEST_MNT/toplevel" TEST_MNT="$TOPLEVEL_MNT" -- cgit v1.2.3