diff options
| author | Andrea Gelmini <[email protected]> | 2021-04-02 18:38:53 -0700 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2021-04-02 18:52:15 -0700 |
| commit | bf169e9f15efbc343b931f20cfad5d2b59c8a821 (patch) | |
| tree | a15662d4490569937a30c715704ff51a698a2473 /module/zfs/vdev_raidz.c | |
| parent | 943df59ed942182427ed50b94a346dc22c4407e6 (diff) | |
Fix various typos
Correct an assortment of typos throughout the code base.
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Matthew Ahrens <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Andrea Gelmini <[email protected]>
Closes #11774
Diffstat (limited to 'module/zfs/vdev_raidz.c')
| -rw-r--r-- | module/zfs/vdev_raidz.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/module/zfs/vdev_raidz.c b/module/zfs/vdev_raidz.c index db753ec16..020b3bc95 100644 --- a/module/zfs/vdev_raidz.c +++ b/module/zfs/vdev_raidz.c @@ -1984,7 +1984,7 @@ raidz_reconstruct(zio_t *zio, int *ltgts, int ntgts, int nparity) * 2 4 5 first: increment to 3 * 3 4 5 done * - * This strategy works for dRAID but is less effecient when there are a large + * This strategy works for dRAID but is less efficient when there are a large * number of child vdevs and therefore permutations to check. Furthermore, * since the raidz_map_t rows likely do not overlap reconstruction would be * possible as long as there are no more than nparity data errors per row. |