From d611989fdc176ccb54c24df99fd6c81b1cfff833 Mon Sep 17 00:00:00 2001 From: Brian Behlendorf Date: Sun, 13 Jan 2019 10:11:52 -0800 Subject: [PATCH] Minor spelling corrections Some minor spelling mistakes and typos. No functional changes. Reviewed-by: Neal Gompa Reviewed by: Matt Ahrens Reviewed-by: Giuseppe Di Natale Reviewed-by: bunder2015 Signed-off-by: Brian Behlendorf Closes #8272 --- cmd/ztest/ztest.c | 10 +++++----- module/zfs/zio.c | 6 +++--- 2 files changed, 8 insertions(+), 8 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. diff --git a/module/zfs/zio.c b/module/zfs/zio.c index 86788b33f..9ca53490e 100644 --- a/module/zfs/zio.c +++ b/module/zfs/zio.c @@ -4016,7 +4016,7 @@ zio_encrypt(zio_t *zio) /* * Later passes of sync-to-convergence may decide to rewrite data * in place to avoid more disk reallocations. This presents a problem - * for encryption because this consitutes rewriting the new data with + * for encryption because this constitutes rewriting the new data with * the same encryption key and IV. However, this only applies to blocks * in the MOS (particularly the spacemaps) and we do not encrypt the * MOS. We assert that the zio is allocating or an intent log write @@ -4152,7 +4152,7 @@ zio_checksum_verified(zio_t *zio) * ========================================================================== * Error rank. Error are ranked in the order 0, ENXIO, ECKSUM, EIO, other. * An error of 0 indicates success. ENXIO indicates whole-device failure, - * which may be transient (e.g. unplugged) or permament. ECKSUM and EIO + * which may be transient (e.g. unplugged) or permanent. ECKSUM and EIO * indicate errors that are specific to one I/O, and most likely permanent. * Any other error is presumed to be worse because we weren't expecting it. * ========================================================================== @@ -4323,7 +4323,7 @@ zio_done(zio_t *zio) { /* * Always attempt to keep stack usage minimal here since - * we can be called recurisvely up to 19 levels deep. + * we can be called recursively up to 19 levels deep. */ const uint64_t psize = zio->io_size; zio_t *pio, *pio_next; -- 2.39.5