Lines Matching +full:auto +full:- +full:poll
5 ---------------------------------
49 -1 linear mode
58 (raid-0 and raid-1 only)
78 --------------------------------------
87 that all auto-detected arrays are assembled as partitionable.
90 -------------------------------------------
102 mdadm --assemble --force ....
112 md-mod.start_dirty_degraded=1
116 ------------------
119 Currently, it supports superblock formats ``0.90.0`` and the ``md-1`` format
125 reasons - it is the original superblock format.
128 General Rules - apply for all superblock formats
129 ------------------------------------------------
138 An array should be created by a user-space tool. This will write
165 Specific Rules that apply to format-0 super block arrays, and arrays with no superblock (non-persis…
166 ---------------------------------------------------------------------------------------------------…
181 -------------------
189 contains further md-specific information about the device.
255 multipath), all components must be the same size - or at least
268 is set by user-space. This indicates that metadata is managed
269 by a user-space program. Any device failure or other event that
275 this will be a very large number (or ``none`` since 2.6.30-rc1). At
283 available. It will then appear at md/dev-XXX (depending on the
301 Select/poll works on this file. All changes except between
303 very interesting) are notified. active->active_idle is
327 read-auto
337 if not known, block and switch to write-pending
344 write-pending
347 active-idle
351 This indicates where the write-intent bitmap for the array is
354 It can be one of ``none``, ``file`` or ``[+-]N``.
356 ``[+-]N`` means that many sectors from the start of the metadata.
372 are known to be in-sync.
375 When write-mostly devices are active in a RAID1, write requests
376 to those devices proceed in the background - the filesystem (or
397 to be in-sync. If ``false``, bits will never be cleared.
401 once the array becomes non-degraded, and this fact has been
416 Resync assisted by a write-intent bitmap.
431 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
437 dev-XXX
445 /sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1
461 device is a fully in-sync member of the array
505 Writing ``-writemostly`` clears the writemostly flag.
509 Writing ``-blocked`` clears the ``blocked`` flags and allows writes
516 Writing ``-write_error`` clears writeerrorseen flag.
521 Writing ``-want_replacement`` is allowed at any time. It clears
524 Writing ``replacement`` or ``-replacement`` is only allowed before
528 This file responds to select/poll. Any change to ``faulty``
535 happened while the array was read-only). When using version-1
587 This gives the list of known-but-not-yet-saved-to-disk bad
605 These are symbolic links to the appropriate ``dev-XXX`` entry.
640 user, and the write-intent bitmap is NOT used to
657 This file responds to select/poll. Any important change in the value
658 triggers a poll event. Sometimes the value will briefly be
668 This file responds to select/poll, any increase or decrease
675 that were re-written, or (for ``check``) would have been
676 re-written. As most raid levels work in units of pages rather
681 If the array has a write-intent bitmap, then writing to this
684 numbers or start-end pairs can be written. Multiple numbers
695 is written, then the system-wide value is used. If a value,
696 in kibibytes-per-second is written, then it is used.
700 a locally set or system-wide value.
727 You can use ``select`` or ``poll`` on ``sync_completed`` to wait for
756 requires preread stripes to wait until all full-width stripe-
761 caching. The mode can be "write-throuth" and "write-back". The
762 default is "write-through".