summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoolCold <coolthecold@gmail.com>2011-04-20 15:40:01 +1000
committerNeilBrown <neilb@suse.de>2011-04-20 15:40:01 +1000
commit28a8397852011e323d16a1eecd4787d72b7b9a9e (patch)
treefaa7a9f8b7d194b761a9108024cb3ca74aa79cda
parentfee68723cf6ae00082f70f3eff17fceab2a4f7d7 (diff)
md: Update documentation for sync_min and sync_max entries
linux/Documentation/md.txt is missing description for sync_min and sync_max entries. This patch adds description for sync_min and sync_max entries. Signed-off-by: Roman Ovchinnikov <coolthecold@gmail.com> Signed-off-by: NeilBrown <neilb@suse.de>
-rw-r--r--Documentation/md.txt10
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
within the array where IO will be blocked. This is currently
only supported for raid4/5/6.
+ sync_min
+ sync_max
+ The two values, given as numbers of sectors, indicate a range
+ withing the array where 'check'/'repair' will operate. Must be
+ a multiple of chunk_size. When it reaches "sync_max" it will
+ pause, rather than complete.
+ You can use 'select' or 'poll' on "sync_completed" to wait for
+ that number to reach sync_max. Then you can either increase
+ "sync_max", or can write 'idle' to "sync_action".
+
Each active md device may also have attributes specific to the
personality module that manages it.