[PATCH 1/2] mdmon.8: fix possible typos

Signed-off-by: Namhyung Kim
---
mdmon.8 | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/mdmon.8 b/mdmon.8
index 7939a99..03b31b8 100644
--- a/mdmon.8
+++ b/mdmon.8
@@ -104,7 +104,7 @@ within those disks. MD metadata in comparison defines a 1:1
relationship between a set of block devices and a raid array. For
example to create 2 arrays at different raid levels on a single
set of disks, MD metadata requires the disks be partitioned and then
-each array can created be created with a subset of those partitions. The
+each array can be created with a subset of those partitions. The
supported external formats perform this disk carving internally.
.P
Container devices simply hold references to all member disks and allow
@@ -172,7 +172,7 @@ Note that
is automatically started by
.I mdadm
when needed and so does not need to be considered when working with
-RAID arrays. The only times it is run other that by
+RAID arrays. The only times it is run other than by
.I mdadm
is when the boot scripts need to restart it after mounting the new
root filesystem.
--
1.7.5.2

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH 2/2] md.4: fix possible typos

Signed-off-by: Namhyung Kim
---
md.4 | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/md.4 b/md.4
index 5e79639..378ecc9 100644
--- a/md.4
+++ b/md.4
@@ -128,7 +128,7 @@ have special-purpose uses and is supported.
From release 2.6.28, the
.I md
driver supports arrays with externally managed metadata. That is,
-the metadata is not managed by the kernel by rather by a user-space
+the metadata is not managed by the kernel but rather by a user-space
program which is external to the kernel. This allows support for a
variety of metadata formats without cluttering the kernel with lots of
details.
@@ -468,7 +468,7 @@ scrub starts and is incremented whenever a sector is
found that is a mismatch.
.I md
normally works in units much larger than a single sector and when it
-finds a mismatch, it does not determin exactly how many actual sectors were
+finds a mismatch, it does not determine exactly how many actual sectors were
affected but simply adds the number of sectors in the IO unit that was
used. So a value of 128 could simply mean that a single 64KB check
found an error (128 x 512bytes = 64KB).
@@ -661,7 +661,7 @@ to this file will cause the system-wide setting to have effect.
This is the partner of
.B md/sync_speed_min
and overrides
-.B /proc/sys/dev/raid/spool_limit_max
+.B /proc/sys/dev/raid/speed_limit_max
described below.

.TP
--
1.7.5.2

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 1/2] mdmon.8: fix possible typos

On Fri, 24 Jun 2011 13:26:49 +0900 Namhyung Kim wrote:

> Signed-off-by: Namhyung Kim
> ---
> mdmon.8 | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mdmon.8 b/mdmon.8
> index 7939a99..03b31b8 100644
> --- a/mdmon.8
> +++ b/mdmon.8
> @@ -104,7 +104,7 @@ within those disks. MD metadata in comparison defines a 1:1
> relationship between a set of block devices and a raid array. For
> example to create 2 arrays at different raid levels on a single
> set of disks, MD metadata requires the disks be partitioned and then
> -each array can created be created with a subset of those partitions. The
> +each array can be created with a subset of those partitions. The
> supported external formats perform this disk carving internally.
> .P
> Container devices simply hold references to all member disks and allow
> @@ -172,7 +172,7 @@ Note that
> is automatically started by
> .I mdadm
> when needed and so does not need to be considered when working with
> -RAID arrays. The only times it is run other that by
> +RAID arrays. The only times it is run other than by
> .I mdadm
> is when the boot scripts need to restart it after mounting the new
> root filesystem.


Thanks. I've applied both of these.

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html