summaryrefslogtreecommitdiffstats
path: root/cmd
diff options
context:
space:
mode:
authorBrian Behlendorf <[email protected]>2019-01-13 10:11:52 -0800
committerGitHub <[email protected]>2019-01-13 10:11:52 -0800
commitd611989fdc176ccb54c24df99fd6c81b1cfff833 (patch)
treed98943ca62efac18bc6187b34416530ef6642b40 /cmd
parent61c3391acc988573aaf9e59550f863de4affcb68 (diff)
Minor spelling corrections
Some minor spelling mistakes and typos. No functional changes. Reviewed-by: Neal Gompa <[email protected]> Reviewed by: Matt Ahrens <[email protected]> Reviewed-by: Giuseppe Di Natale <[email protected]> Reviewed-by: bunder2015 <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Closes #8272
Diffstat (limited to 'cmd')
-rw-r--r--cmd/ztest/ztest.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/cmd/ztest/ztest.c b/cmd/ztest/ztest.c
index e98fe8cd3..f7f584358 100644
--- a/cmd/ztest/ztest.c
+++ b/cmd/ztest/ztest.c
@@ -2819,7 +2819,7 @@ ztest_spa_upgrade(ztest_ds_t *zd, uint64_t id)
/*
* If we're configuring a RAIDZ device then make sure that the
- * the initial version is capable of supporting that feature.
+ * initial version is capable of supporting that feature.
*/
switch (ztest_opts.zo_raidz_parity) {
case 0:
@@ -3251,7 +3251,7 @@ ztest_split_pool(ztest_ds_t *zd, uint64_t id)
mutex_enter(&ztest_vdev_lock);
- /* ensure we have a useable config; mirrors of raidz aren't supported */
+ /* ensure we have a usable config; mirrors of raidz aren't supported */
if (zs->zs_mirrors < 3 || ztest_opts.zo_raidz > 1) {
mutex_exit(&ztest_vdev_lock);
return;
@@ -5024,7 +5024,7 @@ ztest_zap(ztest_ds_t *zd, uint64_t id)
dmu_tx_commit(tx);
/*
- * Generate a buch of random entries.
+ * Generate a bunch of random entries.
*/
ints = MAX(ZTEST_ZAP_MIN_INTS, object % ZTEST_ZAP_MAX_INTS);
@@ -5114,7 +5114,7 @@ out:
}
/*
- * Testcase to test the upgrading of a microzap to fatzap.
+ * Test case to test the upgrading of a microzap to fatzap.
*/
void
ztest_fzap(ztest_ds_t *zd, uint64_t id)
@@ -7011,7 +7011,7 @@ ztest_run(ztest_shared_t *zs)
* we need to ensure the removal and scrub complete before running
* any tests that check ztest_device_removal_active. The removal will
* be restarted automatically when the spa is opened, but we need to
- * initate the scrub manually if it is not already in progress. Note
+ * initiate the scrub manually if it is not already in progress. Note
* that we always run the scrub whenever an indirect vdev exists
* because we have no way of knowing for sure if ztest_device_removal()
* fully completed its scrub before the pool was reimported.