Lines Matching refs:devices

121 		then the layouts for 2, 3 and 4 devices	are:
139 		for 2, 3 and 4 devices are:
155 		layouts for 2, 3 and 4 devices are:
176 		RAID levels 4/5/6 allow for addition of devices (metadata
180 		A minimum of devices have to be kept to enforce resilience,
181 		which is 3 devices for raid4/5 and 4 devices for raid6.
189 		E.g. when adding devices to an existing raid set during
204 		to the component devices which can cause data loss during recovery.
217 <#raid_devs>: The number of devices composing the array.
233   # RAID4 - 4 data drives, 1 parity (no metadata devices)
234   # No metadata devices specified to hold superblock/bitmap info
242   # RAID4 - 4 data drives, 1 parity (with metadata devices)
265   2:      <raid_type> <#devices> <health_chars> \
274 Here we can see the RAID type is raid4, there are 5 devices - all of
347 When a block is discarded, some storage devices will return zeroes when
348 the block is read.  These devices set the 'discard_zeroes_data'
349 attribute.  Other devices will return random data.  Confusingly, some
350 devices that advertise 'discard_zeroes_data' will not reliably return
352 from a number of devices to calculate parity blocks and (for performance
354 that the devices be consistent.  Blocks may be discarded in the middle
361 Since the behavior of storage devices is unreliable in this respect,
366 Storage devices that properly support 'discard_zeroes_data' are
369 For trusted devices, the following dm-raid module parameter can be set
382  1.2.0	Handle creation of arrays that contain failed devices.
391  1.5.1	Add ability to restore transiently failed devices on resume.
401  1.9.1	Fix activation of existing RAID 4/10 mapped devices
416  1.14.0	Fix reshape race on small devices.  Fix stripe adding reshape
418 	specific devices are requested via rebuild.  Fix RAID leg