diff options
author | Alexander Fougner <fougner89@gmail.com> | 2016-03-13 14:24:08 +0100 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2016-03-14 13:44:17 +0100 |
commit | 1086629272da5ff3baa4c4f940013a5f4129cc89 (patch) | |
tree | 6eab17700a0cc7ae2bb482fd999b46833847e095 /Documentation/mkfs.btrfs.asciidoc | |
parent | fc4c784b65bbb4517d6a057e3ef50613ff27d485 (diff) |
btrfs-progs: docs: fix spelling errors
Signed-off-by: Alexander Fougner <fougner89@gmail.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'Documentation/mkfs.btrfs.asciidoc')
-rw-r--r-- | Documentation/mkfs.btrfs.asciidoc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/mkfs.btrfs.asciidoc b/Documentation/mkfs.btrfs.asciidoc index 6a492658..0c43a798 100644 --- a/Documentation/mkfs.btrfs.asciidoc +++ b/Documentation/mkfs.btrfs.asciidoc @@ -230,7 +230,7 @@ Other terms commonly used: *block group*:: *chunk*:: a logical range of space of a given profile, stores data, metadata or both; -sometimes the terms are used interchangably +sometimes the terms are used interchangeably + A typical size of metadata block group is 256MiB (filesystem smaller than 50GiB) and 1GiB (larger than 50GiB), for data it's 1GiB. The system block group @@ -274,7 +274,7 @@ the logical blocks to 2 physical locations. Whether there are really 2 physical copies highly depends on the underlying device type. For example, a SSD drive can remap the blocks internally to a single copy thus -deduplicating them. This negates the purpose of increased redunancy and just +deduplicating them. This negates the purpose of increased redundancy and just wastes space. The duplicated data/metadata may still be useful to statistically improve the |