Lines Matching refs:active

125 Devices that have failed or are not yet active can be detached from an
170      active.  This will reconfigure the array.   Otherwise it can only
263      	active_idle and active (which can be frequent and are not
264 	very interesting) are notified.  active->active_idle is
271          May have some settings, but array is not active
283      clean - no pending writes, but otherwise active.
286            if metadata is known, mark 'dirty' and switch to 'active'.
288          If written to an active array that has pending writes, then fails.
289      active
290          fully active: IO and resync can be happening.
294          clean, but writes are blocked waiting for 'active' to be written.
296      active-idle
297          like active, but no writes have been seen for a while (safe_mode_delay).
319      When write-mostly devices are active in a RAID1, write requests
362 	      faulty   - device has been kicked from active use due to
380 	      replacement - device is a replacement for another active
420 	either be 'none' if the device is not active in the array
448 	This can be set whenever the device is not an active member of
471 An active md device will also contain an entry for each active device
508        'idle' will stop an active resync/recovery etc.  There is no
555      When the files are read, they show the currently active value
590      When a resync is active, the value can only ever be increased,
596 Each active md device may also have attributes specific to the
607       number of active entries in the stripe cache