Fix typos in tests/

Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Reviewed-by: Richard Laager <rlaager@wiktel.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
This commit is contained in:
Andrea Gelmini 2019-08-31 01:52:00 +02:00 committed by Tony Hutter
parent 48d8b249c9
commit 8e1f209fa1
7 changed files with 7 additions and 7 deletions

View File

@ -41,7 +41,7 @@
# 3. Fill the filesystem with directories and files. # 3. Fill the filesystem with directories and files.
# 4. Record all the files and directories checksum information. # 4. Record all the files and directories checksum information.
# 5. Damaged one of the virtual disk file. # 5. Damaged one of the virtual disk file.
# 6. Verify the data is correct to prove raidz can withstand 1 devicd is # 6. Verify the data is correct to prove raidz can withstand 1 device is
# failing. # failing.
# #

View File

@ -38,7 +38,7 @@
# space outside of this refreservation. # space outside of this refreservation.
# #
# STRATEGY: # STRATEGY:
# 1. Setting quota and refservation # 1. Setting quota and refreservation
# 2. Verify snapshot can be created, when used =< quota - refreserv # 2. Verify snapshot can be created, when used =< quota - refreserv
# 3. Verify failed to create snapshot, when used > quota - refreserv # 3. Verify failed to create snapshot, when used > quota - refreserv
# #

View File

@ -125,7 +125,7 @@ done
log_note "sizes=$(print -C sizes)" log_note "sizes=$(print -C sizes)"
# #
# Helper furnction for checking that refreservation is calculated properly in # Helper function for checking that refreservation is calculated properly in
# multi-vdev pools. "Properly" is defined as assuming that all vdevs are as # multi-vdev pools. "Properly" is defined as assuming that all vdevs are as
# space inefficient as the worst one. # space inefficient as the worst one.
# #

View File

@ -64,7 +64,7 @@ log_mustnot vdevs_in_pool $TESTPOOL $REMOVEDISK
# #
# Normally, we expect nopwrites to avoid allocating new blocks, but # Normally, we expect nopwrites to avoid allocating new blocks, but
# after a device has been removed the DVAs will get remapped when # after a device has been removed the DVAs will get remapped when
# a L0's indirect bloock is written. This will negate the effects # a L0's indirect block is written. This will negate the effects
# of nopwrite and should result in new allocations. # of nopwrite and should result in new allocations.
# #

View File

@ -115,7 +115,7 @@ for obj in $TESTPOOL/$TESTFS $OBJ_LIST; do
# #
# Due to the way space is consumed and released by metadata we # Due to the way space is consumed and released by metadata we
# can't do an exact check here, but we do do a basic sanity # can't do an exact check here, but we do a basic sanity
# check. # check.
# #
log_must within_limits $space_avail $new_space_avail $RESV_TOLERANCE log_must within_limits $space_avail $new_space_avail $RESV_TOLERANCE

View File

@ -85,7 +85,7 @@ resv_size_set=`expr $resv_space_avail / $num_resv_fs`
# #
# We set the reservations now, rather than when we created the filesystems # We set the reservations now, rather than when we created the filesystems
# to allow us to take into account space used by the filsystem metadata # to allow us to take into account space used by the filesystem metadata
# #
# Note we don't set a reservation on the first filesystem we created, # Note we don't set a reservation on the first filesystem we created,
# hence num=1 rather than zero below. # hence num=1 rather than zero below.

View File

@ -343,7 +343,7 @@ function getds_with_suffix
} }
# #
# Output inherited properties whitch is edited for file system # Output inherited properties which is edited for file system
# #
function fs_inherit_prop function fs_inherit_prop
{ {