diff options
| author | Christoph Anton Mitterer <mail@christoph.anton.mitterer.name> | 2013-07-10 22:42:46 +0200 |
|---|---|---|
| committer | Christoph Anton Mitterer <mail@christoph.anton.mitterer.name> | 2013-07-10 23:32:22 +0200 |
| commit | 956a13fb850321bed8568dfa8692c0c323538d7c (patch) | |
| tree | a8de7b15b1ef93648650899884472b641fc2182c /mdmon.8 | |
| parent | 3eff7c1d2fd658df69d8379cb87f3a766dd5ab5c (diff) | |
align spelling of “RAID” and RAID levels
* Aligned the spelling of “RAID” to use captial letters in all places.
* Aligned the spelling of the RAID level names (LINEAR, RAID1, …) to use capital
letters in all places, except for the string “faulty” in places where not the
RAID level was meant.
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Diffstat (limited to 'mdmon.8')
| -rw-r--r-- | mdmon.8 | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -101,8 +101,8 @@ call is still required. External metadata formats, like DDF, differ from the native MD metadata formats in that they define a set of disks and a series of sub-arrays 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 +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 be created with a subset of those partitions. The supported external formats perform this disk carving internally. |