Lines Matching refs:an

63 For this reason, md will normally refuse to start such an array.  This
69 filesystem on it.  In order to support this booting from such an
98 It is 'assembled' by associating each of these devices with an
108 When an array is assembled, it is first initialized with the
121 Once started, new devices can be added.  They should have an
125 Devices that have failed or are not yet active can be detached from an
167      will be empty.  If an array is being resized this will contain
171      be set while assembling an array.
174      in an e.g. raid5, the array size must first be reduced by
183      of 2.  This can only be set while assembling an array
188      levels.  It can be written while assembling an array.
208      potentially have 2 values, an old and a new value.  If these
248      When an md array has seen no write requests for a certain period
288          If written to an active array that has pending writes, then fails.
310      single bit.  For RAID456, it is a portion of an individual
345 As component devices are added to an md array, they appear in the 'md'
356         A file containing an image of the superblock read from, or
392 		to complete and possibly simulates an error.
405 	or 'blocked' causes an event.
414 	This value can be written while assembling an array thus
415 	providing an ongoing count for arrays with metadata managed by
421         (i.e. is a spare or has failed) or an integer less than the
423 	it currently fills.  This can only be set while assembling an
435 	component_size.  This can be written while assembling an
448 	This can be set whenever the device is not an active member of
471 An active md device will also contain an entry for each active device
508        'idle' will stop an active resync/recovery etc.  There is no
525       arrays is degraded.  So an optimal array will show '0'.  A
528       in the count of missing devices will trigger an event.