diff options
| author | Namhyung Kim <namhyung@gmail.com> | 2011-06-24 06:26:49 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2011-06-28 08:36:42 +0200 |
| commit | 2f48b33d1d7da25cd54edf32edeb0a59a7f75f43 (patch) | |
| tree | af7d69c7b1b450494302f309e31a6ac86a911842 /mdmon.8 | |
| parent | Show DELAYED, PENDING status of resync process in "--detail" (diff) | |
| download | mdadm-2f48b33d1d7da25cd54edf32edeb0a59a7f75f43.tar.xz mdadm-2f48b33d1d7da25cd54edf32edeb0a59a7f75f43.zip | |
mdmon.8: fix possible typos
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdmon.8')
| -rw-r--r-- | mdmon.8 | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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. |