Lines Matching full:be
7 Tools that manage md devices can be found at
82 This autodetection may be suppressed with the kernel parameter
84 superblock can be autodetected and run at boot time.
94 ``dirty`` means that the parity cannot be trusted, and the fact that it
96 be reconstructed (due to no parity).
108 arrays to be started.
136 be accessed.
138 An array should be created by a user-space tool. This will write
147 format is to be used. The minor number might be used to tune handling
157 Once started, new devices can be added. They should have an
158 appropriate superblock written to them, and then be passed in with
161 Devices that have failed or are not yet active can be detached from an
168 An array can be ``created`` by describing the array (level, chunksize
172 Then uninitialized devices can be added with ADD_NEW_DISK. The
176 Once started with RUN_ARRAY, uninitialized spares can be added with
198 to it, which may be a name like the above, or may be a number
204 will be empty. If an array is being resized this will contain
206 Some raid levels allow this value to be set while the array is
208 be set while assembling an array.
209 A change to this attribute will not be permitted if it would
211 in an e.g. raid5, the array size must first be reduced by
219 The size should be at least PAGE_SIZE (4k) and should be a power
220 of 2. This can only be set while assembling an array
225 levels. It can be written while assembling an array.
228 This can be used to artificially constrain the available space in
229 the array to be less than is actually available on the combined
234 array to be whatever size is actually available based on
237 This can be used to reduce the size of the array before reducing
255 multipath), all components must be the same size - or at least
258 and can be read from here. Writing to this value may resize
264 about the array. It can be 0.90 (traditional format), 1.0, 1.1,
267 Alternately it can be ``external:`` followed by a string which
270 requires a metadata update will cause array activity to be
275 this will be a very large number (or ``none`` since 2.6.30-rc1). At
280 This file can be written but not read. The value written should
281 be a block device number as major:minor. e.g. 8:0
282 This will cause that device to be attached to the array, if it is
288 of time, it will be marked as ``clean``. When another write
297 state of the array. In many cases, the state can be set by
299 cannot be explicitly set, and some transitions are not allowed.
302 Active_idle and active (which can be frequent and are not
318 All IO requests will block. The array can be reconfigured.
341 fully active: IO and resync can be happening.
345 clean, but writes are blocked waiting for ``active`` to be written.
354 It can be one of ``none``, ``file`` or ``[+-]N``.
355 ``file`` may later be extended to ``file:/file/name``
363 The size, in bytes, of the chunk which will be represented by a
370 be cleared. In the current implementation, a bit will be cleared
372 are known to be in-sync.
383 This can be either ``internal`` or ``external``.
396 bitmap will be cleared when the corresponding blocks are thought
397 to be in-sync. If ``false``, bits will never be cleared.
400 When metadata is managed externally, it should be set to true
406 shutdown. It can be:
453 which can be a comma separated list of:
464 device will only be subject to read
487 should be replaced, either due to errors or
497 This can be written to.
533 this device but have not caused the device to be evicted from
538 This value can be written while assembling an array thus
544 either be ``none`` if the device is not active in the array
547 it currently fills. This can only be set while assembling an
548 array. A device for which this is set is assumed to be working.
552 start) where data from the array will be stored. Any part of
557 The amount of the device, after the offset, that can be used
558 for storage of data. This will normally be the same as the
559 component_size. This can be written while assembling an
561 written, it will be rejected.
565 sectors from the start of the device which are known to be
572 This can be set whenever the device is not an active member of
582 is too big to fit in a page, it will be truncated. Writing
589 to fit in a page, it will be truncated. Writing to this file
604 So for a 3 drive array there will be rd0, rd1, rd2.
618 a text file that can be used to monitor and control the rebuild
619 process. It contains one word which can be one of:
643 This file is writable, and each of the strings that could be
647 guarantee that another resync/recovery may not be automatically
648 started again, though some event will be needed to trigger
651 ``resync`` or ``recovery`` can be used to restart the
658 triggers a poll event. Sometimes the value will briefly be
659 ``recover`` if a recovery seems to be needed, but cannot be
677 than sectors, this may be larger than the number of actual errors
684 numbers or start-end pairs can be written. Multiple numbers
685 can be separated by a space.
688 They should be scaled by the bitmap_chunksize.
705 sectors in total that could need to be processed. The two
719 within the array where IO will be blocked. This is currently
724 within the array where ``check``/``repair`` will operate. Must be
732 When a resync is active, the value can only ever be increased,
753 number of times a stripe requiring preread will be bypassed by
761 caching. The mode can be "write-throuth" and "write-back". The
765 NVMe stream ID to be set for each PPL write request.