Lines Matching refs:array
16 or, to assemble a partitionable array:
57 If a raid5 or raid6 array is both dirty and degraded, it could have
63 For this reason, md will normally refuse to start such an array. This
64 requires the sysadmin to take action to explicitly start the array
68 This option is not really available if the array has the root
70 array, md supports a module parameter "start_dirty_degraded" which,
95 An array is 'created' by writing appropriate superblocks to all
102 An array should be created by a user-space tool. This will write
103 superblocks to all devices. It will usually mark the array as
108 When an array is assembled, it is first initialized with the
119 The array is started with the RUN_ARRAY ioctl.
126 array using HOT_REMOVE_DISK.
133 An array can be 'created' by describing the array (level, chunksize
139 and its role in the array.
159 If no raid level has been set yet (array is still being
166 in a fully functional array. If this is not yet known, the file
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
170 active. This will reconfigure the array. Otherwise it can only
171 be set while assembling an array.
173 reduce the size of the array. To reduce the number of drives
174 in an e.g. raid5, the array size must first be reduced by
180 of the array is conceptually divided into chunks and consecutive
183 of 2. This can only be set while assembling an array
186 The "layout" for the array for the particular level. This is
188 levels. It can be written while assembling an array.
192 the array to be less than is actually available on the combined
195 array (e.g. adding devices) will not cause the size to change.
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
206 the array where "reshape" is up to. If this is set, the three
218 part or the geometry of the array. It is measured in sectors
220 the array if the personality supports it (raid1, raid5, raid6),
225 about the array. It can be 0.90 (traditional format), 1.0, 1.1,
231 requires a metadata update will cause array activity to be
237 array creation it will default to 0, though starting the array as
243 This will cause that device to be attached to the array, if it is
248 When an md array has seen no write requests for a certain period
250 request arrives, the array is marked as 'dirty' before the write
258 state of the array. In many cases, the state can be set by
271 May have some settings, but array is not active
273 When written, doesn't tear down array, but just stops it
275 All IO requests will block. The array can be reconfigured.
276 Writing this, if accepted, will block until array is quiessent
284 When written to inactive array, starts without resync
288 If written to an active array that has pending writes, then fails.
291 When written to inactive array, starts with resync
300 This indicates where the write-intent bitmap for the array is
311 device. For RAID10, it is a portion of the array. For RAID1, it
337 degraded array, or if the array becomes degraded during a write.
339 once the array becomes non-degraded, and this fact has been
345 As component devices are added to an md array, they appear in the 'md'
360 A file recording the current state of the device in the array
365 in_sync - device is a fully in-sync member of the array
387 Writing "remove" removes the device from the array.
401 starting the array. It sets or clears the flag.
410 the array (either because they were corrected or because they
411 happened while the array was read-only). When using version-1
412 metadata, this value persists across restarts of the array.
414 This value can be written while assembling an array thus
419 This gives the role that the device has in the array. It will
420 either be 'none' if the device is not active in the array
422 'raid_disks' number for the array indicating which position
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
436 array. If a value less than the current component_size is
449 the array, either before the array is activated, or before
472 in the array. These are named
476 where 'NN' is the position in the array, starting from 0.
477 So for a 3 drive array there will be rd0, rd1, rd2.
525 arrays is degraded. So an optimal array will show '0'. A
540 If the array has a write-intent bitmap, then writing to this
551 however they only apply to the particular array.
576 within the array where IO will be blocked. This is currently
582 within the array where 'check'/'repair' will operate. Must be