diff options
| author | Namhyung Kim <namhyung@gmail.com> | 2011-06-24 06:26:50 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2011-06-28 08:36:42 +0200 |
| commit | 1e49aaa0696e843d5ec0ae6709558e0fe51afc06 (patch) | |
| tree | af051edf21d2837afd0cdd77e052f2ba88725599 /md.4 | |
| parent | mdmon.8: fix possible typos (diff) | |
| download | mdadm-1e49aaa0696e843d5ec0ae6709558e0fe51afc06.tar.xz mdadm-1e49aaa0696e843d5ec0ae6709558e0fe51afc06.zip | |
md.4: fix possible typos
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'md.4')
| -rw-r--r-- | md.4 | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -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 |