Lines Matching refs:of

34 		- RAID10: Striped Mirrors (aka 'Striping on top of mirrors')
39 Reference: Chapter 4 of
42 <#raid_params>: The number of parameters that follow.
44 <raid_params> consists of
56 Interval between runs of the bitmap daemon that
66 The region_size multiplied by the number of regions is the
67 logical size of the array. The bitmap records the device
72 These two options are used to alter the default layout of
73 a RAID10 configuration. The number of copies is can be
76 is "near". Near copies are what most people think of with
119 <#raid_devs>: The number of devices composing the array.
120 Each device consists of two entries. The first is the device
132 # Chunk size of 1MiB
140 # Chunk size of 1MiB, force RAID initialization,
152 above with "sync" or "nosync" always output ahead of the other
153 arguments, regardless of the order used when originally loading the table.
157 'dmsetup status' yields information on the state and health of the array.
167 Here we can see the RAID type is raid4, there are 5 devices - all of
169 recovery. Here is a fuller description of the individual fields:
173 <sync_ratio> The ratio indicating how much of the array has undergone
176 of "resync" or "recover" can be considered complete.
177 <sync_action> One of the following possible states:
185 check - A user-initiated full check of the array is
187 checked for consistency. The number of
194 <mismatch_cnt> The number of discrepancies found between mirror copies
196 This value is valid only after a "check" of the array
197 is performed. A healthy array has a 'mismatch_cnt' of 0.
208 "check" - Initiate a check (i.e. a "scrub") of the array.
209 "repair" - Initiate a repair of the array.
215 The implementation of discard support among hardware vendors varies.
221 from a number of devices to calculate parity blocks and (for performance
224 of a RAID 4/5/6 stripe and if subsequent read results are not
230 Since the behavior of storage devices is unreliable in this respect,
233 expense of losing some performance.
247 1.2.0 Handle creation of arrays that contain failed devices.
254 1.5.0 Add message interface to allow manipulation of the sync_action.