Browse Source

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>
CoolCold 12 years ago
parent
commit
0baac4db56
1 changed files with 6 additions and 7 deletions
  1. 6 7
      Documentation/md.txt

+ 6 - 7
Documentation/md.txt

@@ -566,13 +566,6 @@ also have
      when it reaches the current sync_max (below) and possibly at
      when it reaches the current sync_max (below) and possibly at
      other times.
      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
    sync_speed
      This shows the current actual speed, in K/sec, of the current
      This shows the current actual speed, in K/sec, of the current
      sync_action.  It is averaged over the last 30 seconds.
      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
      that number to reach sync_max.  Then you can either increase
      "sync_max", or can write 'idle' to "sync_action".
      "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
 Each active md device may also have attributes specific to the
 personality module that manages it.
 personality module that manages it.