Lines Matching refs:md

1 Tools that manage md devices can be found at
8 You can boot with your md device with the following kernel command
12   md=<md device no.>,<raid level>,<chunk size factor>,<fault level>,dev0,dev1,...,devn
15   md=<md device no.>,dev0,dev1,...,devn
17   md=d<md device no.>,dev0,dev1,...,devn
19 md device no. = the number of the md device ... 
39 e:\loadlin\loadlin e:\zimage root=/dev/md0 md=0,0,4,0,/dev/hdb2,/dev/hdc3 ro
45 When md is compiled into the kernel (not as module), partitions of
63 For this reason, md will normally refuse to start such an array.  This
70 array, md supports a module parameter "start_dirty_degraded" which,
76    md-mod.start_dirty_degraded=1
82 The md driver can support a variety of different superblock formats.
83 Currently, it supports superblock formats "0.90.0" and the "md-1" format
99 particular md virtual device.  Once it is completely assembled, it can
104 'unclean', or with some devices missing so that the kernel md driver
148 md devices appear in sysfs (/sys) as regular block devices,
152 Each 'md' device will contain a subdirectory called 'md' which
153 contains further md-specific information about the device.
155 All md devices contain:
244      available.  It will then appear at md/dev-XXX (depending on the
248      When an md array has seen no write requests for a certain period
329      managed by the md module.
345 As component devices are added to an md array, they appear in the 'md'
353 	     /sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1
471 An active md device will also contain an entry for each active device
480        cat /sys/block/md*/md/rd*/state
485 Active md devices for levels that support data redundancy (1,4,5,6,10)
532       performing 'resync', md will count the number of errors that are
596 Each active md device may also have attributes specific to the