aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/md.txt
diff options
context:
space:
mode:
authorJonathan Brassow <jbrassow@redhat.com>2013-04-23 21:42:42 -0400
committerNeilBrown <neilb@suse.de>2013-04-23 21:42:42 -0400
commitb6fec069af5a26439f7d36cb3d4f5dd1378af7e2 (patch)
tree20aa3c5d56fbe3ec7d3d2ecb99af7c9d7d159558 /Documentation/md.txt
parentc0b32972fb1e1110101702f096c0877afcab9f1d (diff)
MD: Fix typos in MD documentation
MD: Fix some typos/grammer in MD documentation Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Signed-off-by: Jonathan Brassow <jbrassow@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'Documentation/md.txt')
-rw-r--r--Documentation/md.txt16
1 files changed, 8 insertions, 8 deletions
diff --git a/Documentation/md.txt b/Documentation/md.txt
index 993fba37b7d1..e0ddd327632d 100644
--- a/Documentation/md.txt
+++ b/Documentation/md.txt
@@ -119,7 +119,7 @@ device to add.
119The array is started with the RUN_ARRAY ioctl. 119The array is started with the RUN_ARRAY ioctl.
120 120
121Once started, new devices can be added. They should have an 121Once started, new devices can be added. They should have an
122appropriate superblock written to them, and then passed be in with 122appropriate superblock written to them, and then be passed in with
123ADD_NEW_DISK. 123ADD_NEW_DISK.
124 124
125Devices that have failed or are not yet active can be detached from an 125Devices that have failed or are not yet active can be detached from an
@@ -131,7 +131,7 @@ Specific Rules that apply to format-0 super block arrays, and
131------------------------------------------------------------- 131-------------------------------------------------------------
132 132
133An array can be 'created' by describing the array (level, chunksize 133An array can be 'created' by describing the array (level, chunksize
134etc) in a SET_ARRAY_INFO ioctl. This must has major_version==0 and 134etc) in a SET_ARRAY_INFO ioctl. This must have major_version==0 and
135raid_disks != 0. 135raid_disks != 0.
136 136
137Then uninitialized devices can be added with ADD_NEW_DISK. The 137Then uninitialized devices can be added with ADD_NEW_DISK. The
@@ -426,7 +426,7 @@ Each directory contains:
426 offset 426 offset
427 This gives the location in the device (in sectors from the 427 This gives the location in the device (in sectors from the
428 start) where data from the array will be stored. Any part of 428 start) where data from the array will be stored. Any part of
429 the device before this offset us not touched, unless it is 429 the device before this offset is not touched, unless it is
430 used for storing metadata (Formats 1.1 and 1.2). 430 used for storing metadata (Formats 1.1 and 1.2).
431 431
432 size 432 size
@@ -440,7 +440,7 @@ Each directory contains:
440 When the device is not 'in_sync', this records the number of 440 When the device is not 'in_sync', this records the number of
441 sectors from the start of the device which are known to be 441 sectors from the start of the device which are known to be
442 correct. This is normally zero, but during a recovery 442 correct. This is normally zero, but during a recovery
443 operation is will steadily increase, and if the recovery is 443 operation it will steadily increase, and if the recovery is
444 interrupted, restoring this value can cause recovery to 444 interrupted, restoring this value can cause recovery to
445 avoid repeating the earlier blocks. With v1.x metadata, this 445 avoid repeating the earlier blocks. With v1.x metadata, this
446 value is saved and restored automatically. 446 value is saved and restored automatically.
@@ -468,7 +468,7 @@ Each directory contains:
468 468
469 469
470 470
471An active md device will also contain and entry for each active device 471An active md device will also contain an entry for each active device
472in the array. These are named 472in the array. These are named
473 473
474 rdNN 474 rdNN
@@ -482,7 +482,7 @@ will show 'in_sync' on every line.
482 482
483 483
484 484
485Active md devices for levels that support data redundancy (1,4,5,6) 485Active md devices for levels that support data redundancy (1,4,5,6,10)
486also have 486also have
487 487
488 sync_action 488 sync_action
@@ -494,7 +494,7 @@ also have
494 failed/missing device 494 failed/missing device
495 idle - nothing is happening 495 idle - nothing is happening
496 check - A full check of redundancy was requested and is 496 check - A full check of redundancy was requested and is
497 happening. This reads all block and checks 497 happening. This reads all blocks and checks
498 them. A repair may also happen for some raid 498 them. A repair may also happen for some raid
499 levels. 499 levels.
500 repair - A full check and repair is happening. This is 500 repair - A full check and repair is happening. This is
@@ -522,7 +522,7 @@ also have
522 522
523 degraded 523 degraded
524 This contains a count of the number of devices by which the 524 This contains a count of the number of devices by which the
525 arrays is degraded. So an optimal array with show '0'. A 525 arrays is degraded. So an optimal array will show '0'. A
526 single failed/missing drive will show '1', etc. 526 single failed/missing drive will show '1', etc.
527 This file responds to select/poll, any increase or decrease 527 This file responds to select/poll, any increase or decrease
528 in the count of missing devices will trigger an event. 528 in the count of missing devices will trigger an event.