Fix spelling

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov Reviewed-by: Giuseppe Di Natale <dinatale2@llnl.gov>> Reviewed-by: George Melikov <mail@gmelikov.ru> Reviewed-by: Haakan T Johansson <f96hajo@chalmers.se> Closes #5547 Closes #5543
2026-05-22 18:40:43 +03:00 · 2017-01-03 18:31:18 +01:00
parent a5e046eaac
commit 4e33ba4c38
132 changed files with 170 additions and 170 deletions
@@ -914,7 +914,7 @@ function partition_disk	#<slice_size> <whole_disk_name>	<total_slices>
 #	filenum:    the maximum number of files per subdirectory
 #	bytes:	    number of bytes to write
 #	num_writes: numer of types to write out bytes
-#	data:	    the data that will be writen
+#	data:	    the data that will be written
 #
 #	E.g.
 #	file_fs /testdir 20 25 1024 256 0
@@ -1836,7 +1836,7 @@ function is_pool_scrub_stopped #pool
 }

 #
-# Use create_pool()/destroy_pool() to clean up the infomation in
+# Use create_pool()/destroy_pool() to clean up the information in
 # in the given disk to avoid slice overlapping.
 #
 function cleanup_devices #vdevs
@@ -237,7 +237,7 @@ function usr_exec #<commands> [...]
 }

 #
-# Count how many ACEs for the speficied file or directory.
+# Count how many ACEs for the specified file or directory.
 #
 # $1 file or directroy name
 #
@@ -34,7 +34,7 @@
 #
 # STRATEGY:
 # 1. create pools based on a valid vdev
-# 2. create a filesytem on this pool and set the compression property to gzip1-9
+# 2. create a filesystem on this pool and set the compression property to gzip1-9
 # 3. set the pool's bootfs property to filesystem we just configured which
 #    should fail
 #
@@ -21,7 +21,7 @@
 # Check that we can create FS with any supported casesensitivity value.
 #
 # STRATEGY:
-# For all suported casesensitivity values:
+# For all supported casesensitivity values:
 # 1. Create FS with given casesensitivity value.

 verify_runnable "global"
@@ -37,7 +37,7 @@
 # return an error.
 #
 # STRATEGY:
-# 1. Create an array containg bad zdb parameters.
+# 1. Create an array containing bad zdb parameters.
 # 2. For each element, execute the sub-command.
 # 3. Verify it returns an error.
 #
@@ -35,7 +35,7 @@
 # DESCRIPTION:
 #	'zfs clone' should fail with inapplicable scenarios, including:
 #		* Null arguments
-#		* non-existant snapshots.
+#		* non-existent snapshots.
 #		* invalid characters in ZFS namesapec
 #		* Leading slash in the target clone name
 #		* The argument contains an empty component.
@@ -146,7 +146,7 @@ typeset -i i
 i=1
 log_must setup_ds

-log_note "Verify zfs clone propery for multiple clones"
+log_note "Verify zfs clone property for multiple clones"
 names=$($ZFS list -rt all -o name $TESTPOOL)
 log_must verify_clones 3 0

@@ -129,25 +129,25 @@ for clone in $child_fs1_snap_clone $child_fs1_snap_clone1; do
 done

 log_note "Verify that 'zfs destroy -r' fails to destroy dataset " \
-	"with clone dependant outside it."
+	"with dependent clone outside it."

 for obj in $child_fs $child_fs1 $ctr $ctr1; do
 	log_mustnot $ZFS destroy -r $obj
 	datasetexists $obj || \
-		log_fail "'zfs destroy -r' fails to keep clone " \
-			"dependant outside the hirearchy."
+		log_fail "'zfs destroy -r' fails to keep dependent " \
+			"clone outside the hirearchy."
 done


 log_note "Verify that 'zfs destroy -R' succeeds to destroy dataset " \
-	"with clone dependant outside it."
+	"with dependent clone outside it."

 log_must $ZFS destroy -R $ctr1
 datasetexists $ctr1 && \
 	log_fail "'zfs destroy -R' fails to destroy dataset with clone outside it."

 log_note "Verify that 'zfs destroy -r' succeeds to destroy dataset " \
-	"without clone dependant outside it."
+	"without dependent clone outside it."

 log_must $ZFS destroy -r $ctr
 datasetexists $ctr && \
@@ -35,7 +35,7 @@

 #
 # DESCRIPTION:
-#	Seperately verify 'zfs destroy -f|-r|-rf|-R|-rR <dataset>' will fail in
+#	Separately verify 'zfs destroy -f|-r|-rf|-R|-rR <dataset>' will fail in
 #       different conditions.
 #
 # STRATEGY:
@@ -50,7 +50,7 @@

 verify_runnable "both"

-log_assert "Seperately verify 'zfs destroy -f|-r|-rf|-R|-rR <dataset>' will " \
+log_assert "Separately verify 'zfs destroy -f|-r|-rf|-R|-rR <dataset>' will " \
 	"fail in different conditions."
 log_onexit cleanup_testenv

@@ -30,7 +30,7 @@

 ################################################################################
 #
-# When using 'zfs destroy -R' on a file system heirarchy that inclues a
+# When using 'zfs destroy -R' on a file system hierarchy that includes a
 # snapshot and a clone of that snapshot, and the snapshot has been
 # defer-destroyed, make sure that the 'zfs destroy -R' works as expected.
 # In particular make sure that libzfs is not confused by the fact that the
@@ -90,7 +90,7 @@ for args in $valid_args; do
 	verify_snapshots
 done

-log_note "Verify invalid arguements"
+log_note "Verify invalid arguments"
 setup_snapshots
 for args in $invalid_args; do
 	log_mustnot $ZFS destroy $TESTPOOL/$TESTFS1$args
@@ -98,7 +98,7 @@ for args in $invalid_args; do
 	log_must verify_snapshots 1
 done

-log_note "Destroy the begining range"
+log_note "Destroy the beginning range"

 log_must $ZFS destroy $TESTPOOL/$TESTFS1@%snap3
 log_must $ZFS destroy $TESTPOOL/$TESTVOL@%snap3
@@ -113,7 +113,7 @@ function cleanup_testenv

 #
 # Delete volume and related datasets from list, if the test cases was
-# runing in local zone. Then check them are existed or non-exists.
+# running in local zone. Then check them are existed or non-exists.
 #
 # $1   function name
 # $2-n datasets name
@@ -36,7 +36,7 @@
 #	1. Create a multiple depth filesystem.
 #	2. 'zfs get -d <n>' to get the output.
 #	3. 'zfs get -r|egrep' to get the expected output.
-#	4. Compare the two outputs, they shoud be same.
+#	4. Compare the two outputs, they should be same.
 #

 verify_runnable "both"
@@ -85,7 +85,7 @@ log_must $ZFS set mountpoint=$mntpnt1 $fs1
 log_must $ZFS mount $fs1
 log_must $LS $testfile1 $mntpnt1/$TESTFILE2

-# Verify $TESTFILE2 was not created in $fs, and $fs is accessable again.
+# Verify $TESTFILE2 was not created in $fs, and $fs is accessible again.
 log_mustnot $LS $mntpnt/$TESTFILE2
 log_must $LS $testfile

@@ -40,7 +40,7 @@
 #	1. Create multiple snapshots and a clone to a middle point snapshot
 #	2. Promote the clone filesystem
 #	3. Verify the origin filesystem and promoted filesystem include
-#	   correct datasets seperated by the clone point.
+#	   correct datasets separated by the clone point.
 #

 verify_runnable "both"
@@ -30,7 +30,7 @@

 #
 # DESCRIPTION:
-#	Seperately verify 'zfs rollback ''|-f|-r|-rf|-R|-rR will fail in
+#	Separately verify 'zfs rollback ''|-f|-r|-rf|-R|-rR will fail in
 #	different conditions.
 #
 # STRATEGY:
@@ -53,7 +53,7 @@ function cleanup
 	done
 }

-log_assert "Seperately verify 'zfs rollback ''|-f|-r|-rf will fail in " \
+log_assert "Separately verify 'zfs rollback ''|-f|-r|-rf will fail in " \
 	"different conditions."
 log_onexit cleanup

@@ -124,7 +124,7 @@ function cleanup_user_prop
 }

 #
-# Random select charactor from the specified charactor set and combine into a
+# Random select character from the specified character set and combine into a
 # random string
 #
 # $1 character set name
@@ -32,7 +32,7 @@
 #	are not in the same pool.
 #
 # STRATEGY:
-#	1. Create 2 separate zpools, zpool name lenghts must be the same.
+#	1. Create 2 separate zpools, zpool name lengths must be the same.
 #	2. Attempt to simultaneously create a snapshot of each pool.
 #	3. Veriy the snapshot creation failed.
 #
@@ -20,7 +20,7 @@
 #
 # STRATEGY
 # 1. Create multiple datasets
-# 2. Create mutiple snapshots with a list of valid and invalid
+# 2. Create multiple snapshots with a list of valid and invalid
 #    snapshot names
 # 3. Verify the valid snpashot creation

@@ -29,7 +29,7 @@

 #
 # DESCRIPTION:
-# Verify that a file system and its dependant are unshared when turn off sharenfs
+# Verify that a file system and its dependent are unshared when turn off sharenfs
 # property.
 #
 # STRATEGY:
@@ -81,10 +81,10 @@ function test_snap_unshare # <mntp> <filesystem>
 	    log_fail "Snapshot $mntpt@snapshot is shared (set sharenfs)."
 }

-log_assert "Verify that a file system and its dependant are unshared."
+log_assert "Verify that a file system and its dependent are unshared."
 log_onexit cleanup

 log_must $ZFS snapshot $TESTPOOL/$TESTFS@snapshot
 test_snap_unshare $TESTDIR $TESTPOOL/$TESTFS

-log_pass "A file system and its dependant are both unshared as expected."
+log_pass "A file system and its dependent are both unshared as expected."
@@ -37,7 +37,7 @@
 #	should run successfully.
 #
 # STRATEGY:
-# 1. Create an array containg each zpool options.
+# 1. Create an array containing each zpool options.
 # 2. For each element, execute the zpool command.
 # 3. Verify it run successfully.
 #
@@ -45,7 +45,7 @@ fi

 if [[ -n $DISK ]]; then
 	#
-        # Use 'zpool create' to clean up the infomation in
+        # Use 'zpool create' to clean up the information in
        # in the given disk to avoid slice overlapping.
        #
 	cleanup_devices $DISK
@@ -47,7 +47,7 @@ fi

 if [[ -n $DISK ]]; then
 	#
-        # Use 'zpool create' to clean up the infomation in
+        # Use 'zpool create' to clean up the information in
        # in the given disk to avoid slice overlapping.
        #
 	cleanup_devices $DISK
@@ -100,7 +100,7 @@ log_assert "Verify all mount & share status of sub-filesystems within a pool \
 	can be restored after import [-Df]."

 setup_filesystem "$DEVICE_FILES" $TESTPOOL1 $TESTFS $TESTDIR1
-# create a heirarchy of filesystem
+# create a hierarchy of filesystem
 for pool in ${pools[@]} ; do
 	log_must $ZFS create $pool/$TESTFS/$TESTCTR
 	log_must $ZFS create $pool/$TESTFS/$TESTCTR/$TESTCTR1
@@ -38,7 +38,7 @@
 # STRATEGY:
 #	1. 'zfs list -d <n>' to get the output.
 #	2. 'zfs list -r|egrep' to get the expected output.
-#	3. Compare the two outputs, they shoud be same.
+#	3. Compare the two outputs, they should be same.
 #

 verify_runnable "both"
@@ -50,7 +50,7 @@ function cleanup
 	$RM -f $TESTDIR/*
 }

-log_assert "Changing blocksize doesn't casue system panic with compression settings"
+log_assert "Changing blocksize doesn't cause system panic with compression settings"
 log_onexit cleanup

 fs=$TESTPOOL/$TESTFS
@@ -60,8 +60,8 @@ if is_linux; then
 # - rename      - mount(8) does not permit non-superuser mounts
 # - zoned	- zones are not supported
 # - destroy     - umount(8) does not permit non-superuser umounts
-# - sharenfs	- sharing requires superuser priviliges
-# - share	- sharing requires superuser priviliges
+# - sharenfs	- sharing requires superuser privileges
+# - share	- sharing requires superuser privileges
 # - readonly	- mount(8) does not permit non-superuser remounts
 #
 set -A perms	create		true		false	\
@@ -32,7 +32,7 @@
 . $STF_SUITE/include/libtest.shlib

 #
-# Create block file or charactor file according to parameter.
+# Create block file or character file according to parameter.
 #
 # $1 device file type
 # $2 file name
@@ -29,7 +29,7 @@
 # or set locally.
 #
 # Format for this file is as follows:
-#	<dataset name>	<dataset type> 	<inital property setting>
+#	<dataset name>	<dataset type> 	<initial property setting>
 #
 # <dataset name> - must be the full dataset name
 #
@@ -157,10 +157,10 @@ function update_recordsize { #dataset init_code
 # The mountpoint property is slightly different from other properties and
 # so is handled here. For all other properties if they are set to a specific
 # value at a higher level in the data hierarchy (i.e. checksum=on) then that
-# value propogates down the hierarchy unchanged, with the source field being
+# value propagates down the hierarchy unchanged, with the source field being
 # set to 'inherited from <higher dataset>'.
 #
-# The mountpoint property is different in that while the value propogates
+# The mountpoint property is different in that while the value propagates
 # down the hierarchy, the value at each level is determined by a combination
 # of the top-level value and the current level in the hierarchy.
 #
@@ -327,7 +327,7 @@ function scan_state { #state-file
 				# set up correctly as specified in the
 				# configX.cfg file (which includes 'set'ting
 				# properties at a higher level and checking
-				# that they propogate down to the lower levels.
+				# that they propagate down to the lower levels.
 				#
 				# Note in a few places here, we use
 				# check_failure, rather than log_must - this
@@ -33,7 +33,7 @@
 # No command is actually run (hence '-:-') but rather this state file is
 # used to verify that the property that was set on the top level pool
 # via the 'local' keyword (in the config1.cfg file) has correctly
-# propogated down the hierarchy.
+# propagated down the hierarchy.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -33,7 +33,7 @@
 # No command is actually run (hence '-:-') but rather this state file is
 # used to verify that the property that was set on the middle level
 # dataset via the 'local' keyword (in the configX.cfg file) has
-# correctly propogated down the hierarchy to the filesystem underneath,
+# correctly propagated down the hierarchy to the filesystem underneath,
 # while leaving the top level pools properties unchanged.
 #
 # *** ASSERTION DESCRIPTION ***
@@ -32,12 +32,12 @@
 #
 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
 # when the bottom filesystem level properties have been set locally results
-# in the top level property values being propogated down the data
+# in the top level property values being propagated down the data
 # hierarchy.
 #
 # Executing inherit -r at the middle level and bottom levels after
 # running it at the top level is somewhat redundant as the top level value
-# should propogate down the entire data hierarchy. Done for completeness
+# should propagate down the entire data hierarchy. Done for completeness
 # sake.
 #
 # *** ASSERTION DESCRIPTION ***
@@ -32,12 +32,12 @@
 #
 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
 # when the bottom and middle level properties have been set locally results
-# in the top level property values being propogated down the data
+# in the top level property values being propagated down the data
 # hierarchy.
 #
 # Note : executing inherit -r at the middle level and bottom levels after
 # running it at the top level is somewhat redundant as the top level value
-# should propogate down the entire data hierarchy. Done for completeness
+# should propagate down the entire data hierarchy. Done for completeness
 # sake.
 #
 # *** ASSERTION DESCRIPTION ***
@@ -40,7 +40,7 @@
 # the bottom level.
 #
 # Executing 'zfs inherit' at the bottom level is somewhat redundant but
-# is done for completness sake.
+# is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -37,7 +37,7 @@
 # to the top level (default) values.
 #
 # Executing 'zfs inherit -r' at the bottom and middle levels after executing
-# at the top level is somewhat redundant but ss done for completness sake.
+# at the top level is somewhat redundant but ss done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -41,7 +41,7 @@
 # the values down to the bottom level.
 #
 # Executing 'zfs inherit' at the bottom level is somewhat redundant but
-# is done for completness sake.
+# is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -34,11 +34,11 @@
 # when the top level and middle level datasets properties are set locally,
 # and the bottom level has inherited its properties from the middle
 # level, results in the top level properties reverting back to their
-# default values and being propogated down to the other datasets in the
+# default values and being propagated down to the other datasets in the
 # hierarchy.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels after executing
-# it at the top level is somewhat redundant but is done for completness sake.
+# it at the top level is somewhat redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -37,7 +37,7 @@
 # levels inheriting the changed values.
 #
 # Executing 'zfs inherit' at the middle and bottom levels is somewhat
-# redundant but is done for completness sake.
+# redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -37,7 +37,7 @@
 # levels inheriting the changed values.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels is somewhat
-# redundant but is done for completness sake.
+# redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -37,7 +37,7 @@
 # levels inheriting the changed values.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels is somewhat
-# redundant but is done for completness sake.
+# redundant but is done for completeness sake.
 #
 # *** ASSERTION DESCRIPTION ***
 #
@@ -33,7 +33,7 @@
 # Verify that executing 'zfs inherit -r' at the top level in the hierarchy
 # when each levels properties are set locally, results in the top level
 # properties reverting back to their default values, and the changed
-# values being propogated down the hierarchy.
+# values being propagated down the hierarchy.
 #
 # Executing 'zfs inherit -r' at the middle and bottom levels after doing so
 # at the top level is somewhat redundant but is done for completeness.
@@ -48,7 +48,7 @@ verify_runnable "global"
 function cleanup
 {
 	#
-	# Essentailly this is the default_cleanup rountine but I cannot get it
+	# Essentailly this is the default_cleanup routine but I cannot get it
 	# to work correctly.  So its reproduced below.  Still need to full
 	# understand why default_cleanup does not work correctly from here.
 	#
@@ -46,7 +46,7 @@ log_assert "nopwrite works on volumes"
 log_must $ZFS set compress=on $origin
 log_must $ZFS set checksum=sha256 $origin
 $DD if=/dev/urandom of=$vol bs=8192 count=4096 conv=notrunc >/dev/null \
-    2>&1 || log_fail "dd into $orgin failed."
+    2>&1 || log_fail "dd into $origin failed."
 $ZFS snapshot $origin@a || log_fail "zfs snap failed"
 log_must $ZFS clone $origin@a $clone
 log_must $ZFS set compress=on $clone
@@ -37,7 +37,7 @@
 #
 # STRATEGY:
 #	1. Setting refquota < quota for parent
-#	2. Create file in sub-filesytem, take snapshot and remove the file
+#	2. Create file in sub-filesystem, take snapshot and remove the file
 #	3. Verify sub-filesystem snapshot will not consume refquota
 #

@@ -37,7 +37,7 @@
 #
 # STRATEGY:
 #	1. Create volume on filesystem
-#	2. Setting quota for parenet filesytem
+#	2. Setting quota for parent filesystem
 #	3. Verify volume refreservation is only limited by volsize
 #	4. Verify volume refreservation can be changed when volsize changed
 #
@@ -33,7 +33,7 @@

 #
 # DESCRIPTION:
-# Create two directory trees in ZFS filesystem, and concurently rename
+# Create two directory trees in ZFS filesystem, and concurrently rename
 # directory across the two trees. ZFS should be able to handle the race
 # situation.
 #
@@ -75,7 +75,7 @@ resv_size_set=`expr $space_avail / 3`
 # for.
 #
 # Any special arguments for create are passed in via the args
-# paramater.
+# parameter.
 #
 function create_resv_destroy { # args1 dataset1 args2 dataset2

@@ -82,7 +82,7 @@ sparse_vol_set_size=$(floor_volsize $sparse_vol_set_size)

 # When initially created, a regular volume's reservation property is set
 # equal to its size (unlike a sparse volume), so we don't need to set it
-# explictly later on
+# explicitly later on
 log_must $ZFS create -V $resv_set $TESTPOOL/$TESTVOL
 log_must $ZFS create -s -V $sparse_vol_set_size $TESTPOOL/$TESTVOL2

@@ -47,7 +47,7 @@
 #

 verify_runnable "global"
-log_assert "system related filesytems can not be renamed or destroyed"
+log_assert "system related filesystems can not be renamed or destroyed"

 typeset rootpool=$(get_rootpool)
 typeset rootfs=$(get_rootfs)
@@ -172,7 +172,7 @@ function cmp_ds_subs
 }

 #
-# Compare all the directores and files in two filesystems
+# Compare all the directories and files in two filesystems
 #
 # $1 source filesystem
 # $2 destination filesystem
@@ -36,7 +36,7 @@
 #	Changes made by 'zfs promote' can be properly received.
 #
 # STRATEGY:
-#	1. Seperatly promote pool clone, filesystem clone and volume clone.
+#	1. Separately promote pool clone, filesystem clone and volume clone.
 #	2. Recursively backup all the POOL and restore in POOL2
 #	3. Verify all the datesets and property be properly received.
 #
@@ -28,7 +28,7 @@
 # 2. Mess up the contents of the stream state file on disk
 # 3. Try ZFS receive, which should fail with a checksum mismatch error
 # 4. ZFS send to the stream state file again using the receive_resume_token
-# 5. ZFS receieve and verify the receive completes successfully
+# 5. ZFS receive and verify the receive completes successfully
 # 6. Repeat steps on an incremental ZFS send
 #

@@ -28,7 +28,7 @@
 # 2. Mess up the contents of the stream state file on disk
 # 3. Try ZFS receive, which should fail with a checksum mismatch error
 # 4. ZFS send to the stream state file again using the receive_resume_token
-# 5. ZFS receieve and verify the receive completes successfully
+# 5. ZFS receive and verify the receive completes successfully
 #

 verify_runnable "both"
@@ -29,7 +29,7 @@
 # 2. Mess up the contents of the stream state file on disk
 # 3. Try ZFS receive, which should fail with a checksum mismatch error
 # 4. ZFS send to the stream state file again using the receive_resume_token
-# 5. ZFS receieve and verify the receive completes successfully
+# 5. ZFS receive and verify the receive completes successfully
 # 6. Repeat steps on an incremental ZFS send
 #

@@ -33,7 +33,7 @@
 # 6. Mess up the contents of the stream state file on disk
 # 7. Try ZFS receive, which should fail with a checksum mismatch error
 # 8. ZFS send to the stream state file again using the receive_resume_token
-# 9. ZFS receieve and verify the receive completes successfully
+# 9. ZFS receive and verify the receive completes successfully
 #

 verify_runnable "both"
@@ -30,7 +30,7 @@
 # 4. Mess up the contents of the stream state file on disk
 # 5. Try ZFS receive, which should fail with a checksum mismatch error
 # 6. ZFS send to the stream state file again using the receive_resume_token
-# 7. ZFS receieve and verify the receive completes successfully
+# 7. ZFS receive and verify the receive completes successfully
 #

 verify_runnable "both"
@@ -55,7 +55,7 @@ do

 		mntpnt=$(get_prop mountpoint $TESTPOOL)
 		#
-		# Create file in pool to trigger writting in slog devices
+		# Create file in pool to trigger writing in slog devices
 		#
 		log_must $DD if=/dev/urandom of=$mntpnt/testfile.$$ count=100

@@ -74,7 +74,7 @@ log_must $THREADSAPPEND ${TESTDIR}/${TESTFILE}
 #
 SIZE=`$LS -l ${TESTDIR}/${TESTFILE} | $AWK '{print $5}'`
 if [[ $SIZE -ne $FILE_SIZE ]]; then
-	log_fail "'The length of ${TESTDIR}/${TESTFILE}' doesnt equal 1310720."
+	log_fail "'The length of ${TESTDIR}/${TESTFILE}' doesn't equal 1310720."
 fi

 log_pass "Multiple thread appends succeeded. File size as expected"