Fix typos

Correct various typos in the comments and tests. Reviewed-by: Ryan Moeller <ryan@iXsystems.com> Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net> Closes #10423
2026-05-22 02:27:36 +03:00 · 2020-06-10 06:24:09 +02:00
parent 7bcb7f0840
commit dd4bc569b9
48 changed files with 74 additions and 73 deletions
@@ -102,7 +102,7 @@ main(int argc, char *argv[])

 		/*
 		 * The argument supplied doesn't exist. Copy the path, and
-		 * remove the trailing slash if presnt.
+		 * remove the trailing slash if present.
 		 */
 		if ((arg = strdup(argv[0])) == NULL)
 			fail("strdup", 1);
@@ -64,7 +64,7 @@ neg_props["guid"] = { "12345" }
 set_fail = {}
 val_fail = {}

-- Test properies that should work
+-- Test properties that should work
 for prop, values in pairs(pos_props) do
    for i, val in ipairs(values) do
        old_val, src = zfs.get_prop(fs, prop)
@@ -94,7 +94,7 @@ for prop, values in pairs(pos_props) do
    end
 end

-- Test properies that should fail
+-- Test properties that should fail
 for prop, expected in pairs(neg_props) do
    exp_val = expected[1]
    exp_err = expected[2]
@@ -31,7 +31,7 @@
 # filesystem, and verify that zfs_ids_to_path behaves correctly with them.
 #
 # STRATEGY:
-# 1. Create a dateset
+# 1. Create a dataset
 # 2. Makes files in the dataset
 # 3. Verify that zfs_ids_to_path outputs the correct format for each one
 #
@@ -19,7 +19,7 @@

 #
 # DESCRIPTION:
-# 'zpool wait' works when waiting for mulitple activities.
+# 'zpool wait' works when waiting for multiple activities.
 #
 # STRATEGY:
 # 1. Create a pool with some data.
@@ -80,4 +80,4 @@ proc_must_exist $pid
 log_must zpool initialize -s $TESTPOOL $DISK1
 bkgrnd_proc_succeeded $pid

-log_pass "'zpool wait' works when waiting for mutliple activities."
+log_pass "'zpool wait' works when waiting for multiple activities."
@@ -23,7 +23,7 @@
 #
 # STRATEGY:
 # 1. Create an empty pool with no activity
-# 2. Run zpool wait with various acitivies, make sure it always returns
+# 2. Run zpool wait with various activities, make sure it always returns
 #    promptly
 #

@@ -38,7 +38,7 @@ function cleanup
 	[[ -d "$TESTDIR" ]] && log_must rm -r "$TESTDIR"
 }

-# Check wether any vdevs in given pool are being trimmed
+# Check whether any vdevs in given pool are being trimmed
 function trim_in_progress
 {
 	typeset pool="$1"
@@ -365,7 +365,7 @@ function verify_destroy
 	typeset cmd=$1
 	typeset flags=$3

-	# This function doesn't currently verifiy the zpool command.
+	# This function doesn't currently verify the zpool command.
 	[[ ${cmd%% *} == "zfs" ]] || return 1
 	[[ $flags =~ "i" ]] || return 1

@@ -158,4 +158,4 @@ for volsize in $VOLSIZES; do
 	destroy_pool $TESTPOOL2
 done

-log_pass "Dateset can be created, mounted & destroy in largest pool succeeded."
+log_pass "Dataset can be created, mounted & destroy in largest pool succeeded."
@@ -40,7 +40,7 @@
 # 1. Create a pool & dataset
 # 2. Call readmmap binary
 # 3. unmount this file system
-# 4. Verify the integrity of this pool & dateset
+# 4. Verify the integrity of this pool & dataset
 #

 verify_runnable "global"
@@ -29,13 +29,13 @@
 # STRATEGY:
 #	1. Create pool with a cache device.
 #	2. Create a an encrypted ZFS file system.
-#	3. Create a random file in the encyrpted file system and random
+#	3. Create a random file in the encrypted file system and random
 #		read for 30 sec.
 #	4. Export pool.
 #	5. Read the amount of log blocks written from the header of the
 #		L2ARC device.
 #	5. Import pool.
-#	6. Mount the encypted ZFS file system.
+#	6. Mount the encrypted ZFS file system.
 #	7. Read the amount of log blocks rebuilt in arcstats and compare to
 #		(5).
 #	8. Check if the labels of the L2ARC device are intact.
@@ -34,7 +34,7 @@
 #	4. Export pool.
 #	5. Read amount of log blocks written.
 #	6. Import pool.
-#	7. Mount the encypted ZFS file system.
+#	7. Mount the encrypted ZFS file system.
 #	8. Read amount of log blocks built.
 #	9. Compare the two amounts
 #	10. Read the file written in (3) and check if l2_hits in
@@ -26,7 +26,7 @@
 # DESCRIPTION:
 # Testing resilver restart logic both with and without the deferred resilver
 # feature enabled, verifying that resilver is not restarted when it is
-# unecessary.
+# unnecessary.
 #
 # STRATEGY:
 # 1. Create a pool
@@ -37,7 +37,7 @@
 # is full. The zfs file system should be stable and works well.
 #
 # STRATEGY:
-# 1. Create a pool & dateset
+# 1. Create a pool & dataset
 # 2. Make directories in the zfs file system
 # 3. Create 50 big files in each directories
 # 4. Test case exit when the disk is full.
@@ -37,7 +37,7 @@
 # is full. The zfs file system should be work well and stable.
 #
 # STRATEGY:
-# 1. Create a pool & dateset
+# 1. Create a pool & dataset
 # 2. Make directories in the zfs file system
 # 3. Create 5000 files in each directories
 # 4. Test case exit when the disk is full
@@ -25,7 +25,7 @@
 # for all fio runs. The ARC is not cleared to ensure that all data is cached.
 #
 # This is basically a copy of the sequential_reads_cached test case, but with
-# a smaller dateset so that we can fit everything into the decompressed, linear
+# a smaller dataset so that we can fit everything into the decompressed, linear
 # space in the dbuf cache.
 #