diff options
| -rw-r--r-- | Documentation/md.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/md.txt b/Documentation/md.txt index a81c7b4790f2..2366b1c8cf19 100644 --- a/Documentation/md.txt +++ b/Documentation/md.txt | |||
| @@ -552,6 +552,16 @@ also have | |||
| 552 | within the array where IO will be blocked. This is currently | 552 | within the array where IO will be blocked. This is currently |
| 553 | only supported for raid4/5/6. | 553 | only supported for raid4/5/6. |
| 554 | 554 | ||
| 555 | sync_min | ||
| 556 | sync_max | ||
| 557 | The two values, given as numbers of sectors, indicate a range | ||
| 558 | withing the array where 'check'/'repair' will operate. Must be | ||
| 559 | a multiple of chunk_size. When it reaches "sync_max" it will | ||
| 560 | pause, rather than complete. | ||
| 561 | You can use 'select' or 'poll' on "sync_completed" to wait for | ||
| 562 | that number to reach sync_max. Then you can either increase | ||
| 563 | "sync_max", or can write 'idle' to "sync_action". | ||
| 564 | |||
| 555 | 565 | ||
| 556 | Each active md device may also have attributes specific to the | 566 | Each active md device may also have attributes specific to the |
| 557 | personality module that manages it. | 567 | personality module that manages it. |
