mdadm.conf.man

   1 MDADM.CONF(5)                                       MDADM.CONF(5)
   2
   3
   4
   5 N\bNA\bAM\bME\bE
   6        mdadm.conf - configuration for management of Software Raid
   7        with mdadm
   8
   9 S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
  10        /etc/mdadm.conf
  11
  12 D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
  13        m\bmd\bda\bad\bdm\bm is a tool for  creating,  managing,  and  monitoring
  14        RAID devices using the m\bmd\bd driver in Linux.
  15
  16        Some  common  tasks, such as assembling all arrays, can be
  17        simplified by describing the devices  and  array  in  this
  18        configuation file.
  19
  20
  21    S\bSY\bYN\bNT\bTA\bAX\bX
  22        The file should be seen as a collection of words separated
  23        by white space (space, tab, or newline).   Any  word  that
  24        beings with a hash sign (#) starts a comment and that word
  25        together with the remainder of the line are ignored.
  26
  27        Any line that start with white space  (space  or  tab)  is
  28        treated  as  though it were a continuation of the previous
  29        line.
  30
  31        Empty lines are ignored, but otherwise each (non continua-
  32        tion) line must start with a keyword as listed below.  The
  33        key words are case insensitve and can be abbreviated to  3
  34        characters.
  35
  36        The keywords are:
  37
  38        D\bDE\bEV\bVI\bIC\bCE\bE A  d\bde\bev\bvi\bic\bce\be  line lists the devices (whole devices or
  39               partitions) that might contain a component of an MD
  40               array.   When  looking  for  the  components  of an
  41               array, m\bmd\bda\bad\bdm\bm will scan these devices and no others.
  42
  43               The  d\bde\bev\bvi\bic\bce\be  line may contain a number of different
  44               devices (separated by spaces) and each device  name
  45               can contain wild cards as defined by g\bgl\blo\bob\bb(7).
  46
  47               Also,  there may be several device lines present in
  48               the file.
  49
  50               For example:
  51
  52               DEVICE /dev/hda* /dev/hdc*
  53               DEV    /dev/sd*
  54               DEVICE /dev/discs/disc*/disc
  55
  56
  57        A\bAR\bRR\bRA\bAY\bY  The ARRAY lines identify actual arrays.  The second
  58               word  on  the line should be the name of the device
  59               where the array  is  normally  assembled,  such  as
  60               /\b/d\bde\bev\bv/\b/m\bmd\bd1\b1.   Subsequent words identify the array. If
  61               multiple identities are given, then the array  must
  62               match  ALL  identities  to  be  considered a match.
  63               Each identity word has a tag, and equals sign,  and
  64               some value.  The options are:
  65
  66
  67            u\buu\bui\bid\bd=\b=  The value should be a 128 bit uuid in hexadeci-
  68                   mal, with punctuation interspersed if  desired.
  69                   This   must   match  the  uuid  stored  in  the
  70                   superblock.
  71
  72            s\bsu\bup\bpe\ber\br-\b-m\bmi\bin\bno\bor\br=\b=
  73                   The value is an  integer  which  indicates  the
  74                   minor  number that was stored in the superblock
  75                   when the array was created. When  an  array  is
  76                   created as /dev/mdX, then the minor number X is
  77                   stored.
  78
  79            d\bde\bev\bvi\bic\bce\bes\bs=\b=
  80                   The value is a comma separated list  of  device
  81                   names.  Precisely these devices will be used to
  82                   assemble the  array.   Note  that  the  devices
  83                   listed  there  must  also be listed on a DEVICE
  84                   line.
  85
  86            l\ble\bev\bve\bel\bl=\b= The value is a raid level.  This  is  not  nor-
  87                   mally  used  to  identify an array, but is sup-
  88                   ported so that the output of
  89
  90                   m\bmd\bda\bad\bdm\bm -\b--\b-e\bex\bxa\bam\bmi\bin\bne\be -\b--\b-s\bsc\bca\ban\bn
  91
  92                   can be use directly in the configuration  file.
  93
  94            d\bdi\bis\bsk\bks\bs=\b= The  value is the number of disks in a complete
  95                   active array.  As with l\ble\bev\bve\bel\bl=\b=  this  is  mainly
  96                   for compatibility with the output of
  97
  98                   m\bmd\bda\bad\bdm\bm -\b--\b-e\bex\bxa\bam\bmi\bin\bne\be -\b--\b-s\bsc\bca\ban\bn.
  99
 100 S\bSE\bEE\bE A\bAL\bLS\bSO\bO
 101        m\bmd\bda\bad\bdm\bm(8), m\bmd\bd(4).
 102
 103
 104
 105
 106                                                     MDADM.CONF(5)