summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCoolCold <coolthecold@gmail.com>2013-06-26 17:46:58 +0200
committerNeilBrown <neilb@suse.de>2013-07-03 01:43:28 +0200
commit0baac4db56b1895743391a348ee9ce4ae5076f9f (patch)
tree2722e7fa74e322e49c5fadb3f7c2d166245ff913
parentMD: Remember the last sync operation that was performed (diff)
downloadlinux-0baac4db56b1895743391a348ee9ce4ae5076f9f.tar.xz
linux-0baac4db56b1895743391a348ee9ce4ae5076f9f.zip
md: remove doubled description for sync_max, merging it within sync_min/sync_max
After last md.txt edits for sync_min/max, sync_max description became doubled. Removing 1st copy, merging details into common sync_min/sync_max section. Signed-off-by: Roman Ovchinnikov <coolthecold@gmail.com> Signed-off-by: NeilBrown <neilb@suse.de>
-rw-r--r--Documentation/md.txt13
1 files changed, 6 insertions, 7 deletions
diff --git a/Documentation/md.txt b/Documentation/md.txt
index e0ddd327632d..fbb2fcbf16b6 100644
--- a/Documentation/md.txt
+++ b/Documentation/md.txt
@@ -566,13 +566,6 @@ also have
when it reaches the current sync_max (below) and possibly at
other times.
- sync_max
- This is a number of sectors at which point a resync/recovery
- process will pause. When a resync is active, the value can
- only ever be increased, never decreased. The value of 'max'
- effectively disables the limit.
-
-
sync_speed
This shows the current actual speed, in K/sec, of the current
sync_action. It is averaged over the last 30 seconds.
@@ -593,6 +586,12 @@ also have
that number to reach sync_max. Then you can either increase
"sync_max", or can write 'idle' to "sync_action".
+ The value of 'max' for "sync_max" effectively disables the limit.
+ When a resync is active, the value can only ever be increased,
+ never decreased.
+ The value of '0' is the minimum for "sync_min".
+
+
Each active md device may also have attributes specific to the
personality module that manages it.