Minor spelling corrections
Some minor spelling mistakes and typos. No functional changes. Reviewed-by: Neal Gompa <ngompa@datto.com> Reviewed by: Matt Ahrens <mahrens@delphix.com> Reviewed-by: Giuseppe Di Natale <guss80@gmail.com> Reviewed-by: bunder2015 <omfgbunder@gmail.com> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #8272
This commit is contained in:
parent
61c3391acc
commit
d611989fdc
|
@ -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);
|
||||
|
||||
|
@ -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.
|
||||
|
|
|
@ -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;
|
||||
|
|
Loading…
Reference in New Issue