Lines Matching refs:be
1 Tools that manage md devices can be found at
47 This autodetection may be suppressed with the kernel parameter
49 superblock can be autodetected and run at boot time.
59 'dirty' means that the parity cannot be trusted, and the fact that it
61 be reconstructed (due to no parity).
72 arrays to be started.
100 be accessed.
102 An array should be created by a user-space tool. This will write
111 format is to be used. The minor number might be used to tune handling
121 Once started, new devices can be added. They should have an
122 appropriate superblock written to them, and then be passed in with
125 Devices that have failed or are not yet active can be detached from an
133 An array can be 'created' by describing the array (level, chunksize
137 Then uninitialized devices can be added with ADD_NEW_DISK. The
141 Once started with RUN_ARRAY, uninitialized spares can be added with
161 to it, which may be a name like the above, or may be a number
167 will be empty. If an array is being resized this will contain
169 Some raid levels allow this value to be set while the array is
171 be set while assembling an array.
172 A change to this attribute will not be permitted if it would
174 in an e.g. raid5, the array size must first be reduced by
182 The size should be at least PAGE_SIZE (4k) and should be a power
183 of 2. This can only be set while assembling an array
188 levels. It can be written while assembling an array.
191 This can be used to artificially constrain the available space in
192 the array to be less than is actually available on the combined
197 array to be whatever size is actually available based on
200 This can be used to reduce the size of the array before reducing
216 multipath), all components must be the same size - or at least
219 and can be read from here. Writing to this value may resize
225 about the array. It can be 0.90 (traditional format), 1.0, 1.1,
228 Alternately it can be "external:" followed by a string which
231 requires a metadata update will cause array activity to be
236 this will be a very large number (or 'none' since 2.6.30-rc1). At
241 This file can be written but not read. The value written should
242 be a block device number as major:minor. e.g. 8:0
243 This will cause that device to be attached to the array, if it is
249 of time, it will be marked as 'clean'. When another write
258 state of the array. In many cases, the state can be set by
260 cannot be explicitly set, and some transitions are not allowed.
263 active_idle and active (which can be frequent and are not
275 All IO requests will block. The array can be reconfigured.
290 fully active: IO and resync can be happening.
294 clean, but writes are blocked waiting for 'active' to be written.
302 It can be one of "none", "file" or "[+-]N".
303 "file" may later be extended to "file:/file/name"
309 The size, in bytes, of the chunk which will be represented by a
315 be cleared. In the current implementation, a bit will be cleared
317 are known to be in-sync.
326 This can be either 'internal' or 'external'.
334 bitmap will be cleared when the corresponding blocks are thought
335 to be in-sync. If 'false', bits will never be cleared.
338 When metadata is managed externally, it should be set to true
361 which can be a comma separated list of
366 writemostly - device will only be subject to read
378 should be replaced, either due to errors or
385 This can be written to.
409 this device but have not caused the device to be evicted from
414 This value can be written while assembling an array thus
420 either be 'none' if the device is not active in the array
423 it currently fills. This can only be set while assembling an
424 array. A device for which this is set is assumed to be working.
428 start) where data from the array will be stored. Any part of
433 The amount of the device, after the offset, that can be used
434 for storage of data. This will normally be the same as the
435 component_size. This can be written while assembling an
437 written, it will be rejected.
441 sectors from the start of the device which are known to be
448 This can be set whenever the device is not an active member of
458 is too big to fit in a page, it will be truncated. Writing
465 to fit in a page, it will be truncated. Writing to this file
477 So for a 3 drive array there will be rd0, rd1, rd2.
489 a text file that can be used to monitor and control the rebuild
490 process. It contains one word which can be one of:
505 This file is writable, and each of the strings that could be
509 guarantee that another resync/recovery may not be automatically
510 started again, though some event will be needed to trigger
512 'resync' or 'recovery' can be used to restart the
518 triggers a poll event. Sometimes the value will briefly be
519 "recover" if a recovery seems to be needed, but cannot be
536 than sectors, this may be larger than the number of actual errors
543 numbers or start-end pairs can be written. Multiple numbers
544 can be separated by a space.
546 They should be scaled by the bitmap_chunksize.
562 sectors in total that could need to be processed. The two
576 within the array where IO will be blocked. This is currently
582 within the array where 'check'/'repair' will operate. Must be
590 When a resync is active, the value can only ever be increased,
609 number of times a stripe requiring preread will be bypassed by