btrfs-progs: fix a bunch of typos

These have been detected by lintian and codespell.

Signed-off-by: Adam Borowski <kilobyte@angband.pl>
Signed-off-by: David Sterba <dsterba@suse.com>

CHANGES

@@ -110,7 +110,7 @@ btrfs-progs-5.13.1 (2021-07-30)
 * build: fix build on musl libc due to missing definition of NAME_MAX
 * check:
   * batch more work into one transaction when clearing v1 free space inodes
-  * detect directoris with wrong number of links
+  * detect directories with wrong number of links
 * libbtrfsutil: fix race between subvolume iterator and deletion
 * mkfs: be more specific about supported profiles for zoned device
 * other:
@@ -215,7 +215,7 @@ btrfs-progs-5.10 (2021-01-18)
     * print percentage of progress
     * add size unit options
   * fi usage: also print free space from statfs
-  * convert: copy full 64 bit timestamp from ext4 if availalble
+  * convert: copy full 64 bit timestamp from ext4 if available
   * check:
     * add ability to repair extent item generation
     * new option to remove leftovers from inode number cache (-o inode_cache)

Documentation/CmdLineConventions

@@ -41,7 +41,7 @@
 * unix commands do one thing and say nothing, we may diverge a bit from that
 * default output is one line shortly describing the action
  * why: running commands from scripts or among many other commands should be
-   noticeable due to progres tracking or for analysis if something goes wrong
+   noticeable due to progress tracking or for analysis if something goes wrong
  * there's a global option to make the commands silent `btrfs -q subcommand`,
    this can be easily scripted eg. storing the global verbosity option in a
    variable, `btrfs $quiet subcommand` and then enabling or disabling as needed

Documentation/btrfs-convert.asciidoc

@@ -48,7 +48,7 @@ machines).
 **BEFORE YOU START**
 
 The source filesystem must be clean, eg. no journal to replay or no repairs
-needed. The respective 'fsck' utility must be run on the source filesytem prior
+needed. The respective 'fsck' utility must be run on the source filesystem prior
 to conversion. Please refer to the manual pages in case you encounter problems.
 
 For ext2/3/4:

Documentation/btrfs-device.asciidoc

@@ -185,7 +185,7 @@ available in the physical space provided by the device, eg. after a device shrin
 group type (Data, Metadata, System) and profile (single, RAID1, ...) allocated
 on the device
 * 'Data,RAID0/3' -- in particular, striped profiles RAID0/RAID10/RAID5/RAID6 with
-the number of devices on which the stripes are allocated, multiple occurences
+the number of devices on which the stripes are allocated, multiple occurrences
 of the same profile can appear in case a new device has been added and all new
 available stripes have been used for writes
 * 'Unallocated' -- remaining space that the filesystem can still use for new

Documentation/btrfs-device.rst

@@ -157,7 +157,7 @@ usage [options] <path> [<path>...]::
           RAID1, ...) allocated on the device
         * *Data,RAID0/3* -- in particular, striped profiles
           RAID0/RAID10/RAID5/RAID6 with the number of devices on which the
-          stripes are allocated, multiple occurences of the same profile can
+          stripes are allocated, multiple occurrences of the same profile can
           appear in case a new device has been added and all new available
           stripes have been used for writes
         * *Unallocated* -- remaining space that the filesystem can still use

Documentation/btrfs-man5.asciidoc

@@ -201,7 +201,7 @@ require.  A read-write mount (or remount) may fail when there are too many devic
 missing, for example if a stripe member is completely missing from RAID0.
 +
 Since 4.14, the constraint checks have been improved and are verified on the
-chunk level, not an the device level. This allows degraded mounts of
+chunk level, not at the device level. This allows degraded mounts of
 filesystems with mixed RAID profiles for data and metadata, even if the
 device number constraints would not be satisfied for some of the profiles.
 +
@@ -884,9 +884,9 @@ There are two ways to detect incompressible data:
 * actual compression attempt - data are compressed, if the result is not smaller,
   it's discarded, so this depends on the algorithm and level
 * pre-compression heuristics - a quick statistical evaluation on the data is
-  peformed and based on the result either compression is performed or skipped,
+  performed and based on the result either compression is performed or skipped,
   the NOCOMPRESS bit is not set just by the heuristic, only if the compression
-  algorithm does not make an improvent
+  algorithm does not make an improvement
 
 PRE-COMPRESSION HEURISTICS
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -898,7 +898,7 @@ incompressible data too but this leads to more overhead as the compression is
 done in another thread and has to write the data anyway. The heuristic is
 read-only and can utilize cached memory.
 
-The tests performed based on the following: data sampling, long repated
+The tests performed based on the following: data sampling, long repeated
 pattern detection, byte frequency, Shannon entropy.
 
 COMPATIBILITY WITH OTHER FEATURES

Documentation/mkfs.btrfs.asciidoc

@@ -69,7 +69,7 @@ changed in version 5.15 to be always 'dup'.
 
 Note that the rotational status can be arbitrarily set by the underlying block
 device driver and may not reflect the true status (network block device, memory-backed
-SCSI devices, real block device behind some additonal device mapper layer,
+SCSI devices, real block device behind some additional device mapper layer,
 etc). It's recommended to always set the options '--data/--metadata' to avoid
 confusion and unexpected results.
 

Documentation/mkfs.btrfs.rst

@@ -65,7 +65,7 @@ OPTIONS
 
                 Note that the rotational status can be arbitrarily set by the underlying block
                 device driver and may not reflect the true status (network block device, memory-backed
-                SCSI devices, real block device behind some additonal device mapper layer,
+                SCSI devices, real block device behind some additional device mapper layer,
                 etc). It's recommended to always set the options *--data/--metadata* to avoid
                 confusion and unexpected results.
 

cmds/device.c

@@ -324,7 +324,7 @@ static int _cmd_device_remove(const struct cmd_struct *cmd,
 	"If 'missing' is specified for <device>, the first device that is",	\
 	"described by the filesystem metadata, but not present at the mount",	\
 	"time will be removed. (only in degraded mode)",			\
-	"If 'cancel' is specified as the only device to delete, request cancelation", \
+	"If 'cancel' is specified as the only device to delete, request cancellation", \
 	"of a previously started device deletion and wait until kernel finishes", \
 	"any pending work. This will not delete the device and the size will be", \
 	"restored to previous state. When deletion is not running, this will fail."

cmds/filesystem.c

@@ -1227,7 +1227,7 @@ static int cmd_filesystem_resize(const struct cmd_struct *cmd,
 		} else if (strcmp(argv[optind], "--") == 0) {
 			/* Separator: options -- non-options */
 		} else if (strncmp(argv[optind], "--", 2) == 0) {
-			/* Emulate what getopt does on unkonwn option */
+			/* Emulate what getopt does on unknown option */
 			optind++;
 			usage_unknown_option(cmd, argv);
 		} else {

cmds/restore.c

@@ -955,7 +955,7 @@ static int search_dir(struct btrfs_root *root, struct btrfs_key *key,
 			do {
 				ret = next_leaf(root, &path);
 				if (ret < 0) {
-					error("search for next leaf faile: %d", ret);
+					error("search for next leaf failed: %d", ret);
 					goto out;
 				} else if (ret > 0) {
 					/* No more leaves to search */

common/utils.c

@@ -645,7 +645,7 @@ struct mnt_entry {
 };
 
 /*
- * Find first occurence of up an option string (as "option=") in @options,
+ * Find first occurrence of up an option string (as "option=") in @options,
  * separated by comma. Return allocated string as "option=value"
  */
 static char *find_option(const char *options, const char *option)
@@ -818,7 +818,7 @@ static void parse_mntinfo_line(char *line, struct mnt_entry *ent)
  *   37 29 0:32 /vol/dir2 /othermnt ro,relatime - btrfs /dev/sda2 ro,ssd,space_cache,subvolid=256,subvol=/vol
  *
  * If we try to find a mount point only using subvol and subvolid from mount
- * options we would get mislead to belive that /othermnt has the same content
+ * options we would get mislead to believe that /othermnt has the same content
  * as /mnt.
  *
  * But, using mountinfo, we have the pathaname _inside_ the filesystem, so we

tests/fsck-tests.sh

@@ -64,7 +64,7 @@ run_one_test() {
 			fi
 			_fail "test failed for case $(basename $testname)"
 		fi
-		# These tests have overriden check_image() and their images may
+		# These tests have overridden check_image() and their images may
 		# have intentional unaligned metadata to trigger subpage
 		# warnings (like fsck/018), skip the check for their subpage
 		# warnings.

tests/fsck-tests/042-half-dropped-inode/test.sh

@@ -9,7 +9,7 @@
 #
 # The way to reproduce the image:
 # - Create a lot of regular file extents for one inode
-#   Using direct IO with small block size is the easiy method
+#   Using direct IO with small block size is the easy method
 # - Modify kernel to commit transaction more aggressively
 #   Two locations are needed:
 #   * btrfs_unlink():