{
    "mode": "man",
    "parameter": "MDADM.CONF",
    "section": "5",
    "url": "https://www.chedong.com/phpMan.php/man/MDADM.CONF/5/json",
    "generated": "2026-11-22T19:06:19Z",
    "synopsis": "/etc/mdadm.conf",
    "sections": {
        "NAME": {
            "content": "mdadm.conf - configuration for management of Software RAID with mdadm\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "/etc/mdadm.conf\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "mdadm  is  a  tool for creating, managing, and monitoring RAID devices using the md driver in\nLinux.\n\nSome common tasks, such as assembling all arrays, can be simplified by describing the devices\nand arrays in this configuration file.\n\n\nSYNTAX\nThe file should be seen as a collection of words separated by white  space  (space,  tab,  or\nnewline).   Any word that beings with a hash sign (#) starts a comment and that word together\nwith the remainder of the line is ignored.\n\nSpaces can be included in a word using quotation characters.  Either  single  quotes  (')  or\ndouble quotes (\") may be used.  All the characters from one quotation character to next iden‐\ntical  character  are  protected  and  will not be used to separate words to start new quoted\nstrings.  To include a single quote it must be between double quotes.  To  include  a  double\nquote it must be between single quotes.\n\nAny line that starts with white space (space or tab) is treated as though it were a continua‐\ntion of the previous line.\n\nEmpty lines are ignored, but otherwise each (non continuation) line must start with a keyword\nas listed below.  The keywords are case insensitive and can be abbreviated to 3 characters.\n\nThe keywords are:\n\nDEVICE A  device  line  lists  the devices (whole devices or partitions) that might contain a\ncomponent of an MD array.  When looking for the components of  an  array,  mdadm  will\nscan these devices (or any devices listed on the command line).\n\nThe  device  line  may contain a number of different devices (separated by spaces) and\neach device name can contain wild cards as defined by glob(7).\n\nAlso, there may be several device lines present in the file.\n\nAlternatively, a device line can contain either or both of the  words  containers  and\npartitions.   The word containers will cause mdadm to look for assembled CONTAINER ar‐\nrays and included them as a source for assembling further arrays.\n\nThe word partitions will cause mdadm to read /proc/partitions and include all  devices\nand  partitions found therein.  mdadm does not use the names from /proc/partitions but\nonly the major and minor device numbers.  It scans /dev to find the name that  matches\nthe numbers.\n\nIf  no  DEVICE line is present in any config file, then \"DEVICE partitions containers\"\nis assumed.\n\nFor example:\n\nDEVICE /dev/hda* /dev/hdc*\nDEV    /dev/sd*\nDEVICE /dev/disk/by-path/pci*\nDEVICE partitions\n\n\nARRAY  The ARRAY lines identify actual arrays.  The second word on the line may be  the  name\nof   the   device  where  the  array  is  normally  assembled,  such  as  /dev/md1  or\n/dev/md/backup.  If the name does not start with a slash ('/'), it is treated as being\nin /dev/md/.  Alternately the word <ignore> (complete  with  angle  brackets)  can  be\ngiven  in  which case any array which matches the rest of the line will never be auto‐\nmatically assembled.  If no device name is given, mdadm will use various heuristics to\ndetermine an appropriate name.\n\nSubsequent words identify the array, or identify the array as a member of a group.  If\nmultiple identities are given, then a component device must match ALL identities to be\nconsidered  a  match.   Each identity word has a tag, and equals sign, and some value.\nThe tags are:\n\nuuid=  The value should be a 128 bit uuid in hexadecimal, with  punctuation  interspersed\nif desired.  This must match the uuid stored in the superblock.\n\nsuper-minor=\nThe  value  is  an integer which indicates the minor number that was stored in the\nsuperblock when the array was created. When an array is created as /dev/mdX,  then\nthe minor number X is stored.\n\ndevices=\nThe value is a comma separated list of device names or device name patterns.  Only\ndevices  with names which match one entry in the list will be used to assemble the\narray.  Note that the devices listed there must also be listed on a DEVICE line.\n\nlevel= The value is a RAID level.  This is not normally used to identify an array, but is\nsupported so that the output of\n\nmdadm --examine --scan\n\ncan be use directly in the configuration file.\n\nnum-devices=\nThe value is the number of devices in a complete active  array.   As  with  level=\nthis is mainly for compatibility with the output of\n\nmdadm --examine --scan.\n\n\nspares=\nThe  value is a number of spare devices to expect the array to have.  The sole use\nof this keyword and value is as follows: mdadm --monitor will report an  array  if\nit is found to have fewer than this number of spares when --monitor starts or when\n--oneshot is used.\n\n\nspare-group=\nThe  value  is  a  textual  name  for a group of arrays.  All arrays with the same\nspare-group name are considered to be part of the same group.  The significance of\na group of arrays is that mdadm will, when monitoring the  arrays,  move  a  spare\ndrive  from one array in a group to another array in that group if the first array\nhad a failed or missing drive but no spare.\n\n\nauto=  This option is rarely needed with mdadm-3.0, particularly if use  with  the  Linux\nkernel  v2.6.28  or  later.   It tells mdadm whether to use partitionable array or\nnon-partitionable arrays and, in the absence of udev, how many  partition  devices\nto  create.  From 2.6.28 all md array devices are partitionable, hence this option\nis not needed.\n\nThe value of this option can be \"yes\" or \"md\" to indicate that a traditional, non-\npartitionable md array should be created, or \"mdp\", \"part\" or \"partition\" to indi‐\ncate that a partitionable md array (only available in linux 2.6 and later)  should\nbe used.  This later set can also have a number appended to indicate how many par‐\ntitions to create device files for, e.g.  auto=mdp5.  The default is 4.\n\n\nbitmap=\nThe  option specifies a file in which a write-intent bitmap should be found.  When\nassembling the array, mdadm will provide this file to the md driver as the  bitmap\nfile.  This has the same function as the --bitmap-file option to --assemble.\n\n\nmetadata=\nSpecify  the  metadata  format  that the array has.  This is mainly recognised for\ncomparability with the output of mdadm -Es.\n\n\ncontainer=\nSpecify that this array is a member array of some container.  The value given  can\nbe either a path name in /dev, or a UUID of the container array.\n\n\nmember=\nSpecify  that  this  array is a member array of some container.  Each type of con‐\ntainer has some way to enumerate member arrays, often a  simple  sequence  number.\nThe  value  identifies  which member of a container the array is.  It will usually\naccompany a \"container=\" word.\n\n\nMAILADDR\nThe mailaddr line gives an E-mail address that alerts should be sent to when mdadm  is\nrunning in --monitor mode (and was given the --scan option).  There should only be one\nMAILADDR  line  and  it  should  have  only one address.  Any subsequent addresses are\nsilently ignored.\n\n\nMAILFROM\nThe mailfrom line (which can only be abbreviated to at least 5  characters)  gives  an\naddress  to  appear  in the \"From\" address for alert mails.  This can be useful if you\nwant to explicitly set a domain, as the default from address is \"root\" with no domain.\nAll words on this line are catenated with spaces to form the address.\n\nNote that this value cannot be set via the mdadm commandline.  It is only settable via\nthe config file.  There should only be one MAILADDR line and it should have  only  one\naddress.  Any subsequent addresses are silently ignored.\n\n\nPROGRAM\nThe  program  line  gives the name of a program to be run when mdadm --monitor detects\npotentially interesting events on any of the arrays that it is monitoring.  This  pro‐\ngram  gets  run  with two or three arguments, they being the Event, the md device, and\npossibly the related component device.\n\nThere should only be one program line and it should be given only  one  program.   Any\nsubsequent programs are silently ignored.\n\n\n\nCREATE The  create  line gives default values to be used when creating arrays, new members of\narrays, and device entries for arrays.\n\nThere should only be one create line.  Any subsequent lines will override the previous\nsettings.\n\nKeywords used in the CREATE line and supported values are:\n\n\nowner=\n\ngroup= These can give  user/group  ids  or  names  to  use  instead  of  system  defaults\n(root/wheel or root/disk).\n\nmode=  An octal file mode such as 0660 can be given to override the default of 0600.\n\nauto=  This  corresponds to the --auto flag to mdadm.  Give yes, md, mdp, part — possibly\nfollowed by a number of partitions — to indicate how missing device entries should\nbe created.\n\n\nmetadata=\nThe name of the metadata format to use if none is explicitly given.  This  can  be\nuseful to impose a system-wide default of version-1 superblocks.\n\n\nnames=yes\nSince  Linux  2.6.29  it  has  been possible to create md devices with a name like\nmdhome rather than just a number, like md3.  mdadm will use the numeric  alterna‐\ntive  by  default as other tools that interact with md arrays may expect only num‐\nbers.  If names=yes is given in mdadm.conf then mdadm will use a name when  appro‐\npriate.   If  names=no is given, then non-numeric md device names will not be used\neven if the default changes in a future release of mdadm.\n\n\nbbl=no By default, mdadm will reserve space for a bad block list (bbl) on all devices in‐\ncluded in or added to any array that supports them.  Setting bbl=no  will  prevent\nthis, so newly added devices will not have a bad block log.\n\n\nHOMEHOST\nThe  homehost  line  gives a default value for the --homehost= option to mdadm.  There\nshould normally be only one other word on the line.  It should either be a host  name,\nor one of the special words <system>, <none> and <ignore>.  If <system> is given, then\nthe gethostname(2) systemcall is used to get the host name.  This is the default.\n\nIf  <ignore> is given, then a flag is set so that when arrays are being auto-assembled\nthe checking of the recorded homehost is disabled.  If <ignore> is given  it  is  also\npossible  to  give  an explicit name which will be used when creating arrays.  This is\nthe only case when there can be more that one other word on  the  HOMEHOST  line.   If\nthere are other words, or other HOMEHOST lines, they are silently ignored.\n\nIf  <none>  is  given,  then the default of using gethostname(2) is over-ridden and no\nhomehost name is assumed.\n\nWhen arrays are created, this host name will be stored in the metadata.   When  arrays\nare  assembled  using  auto-assembly,  arrays which do not record the correct homehost\nname in their metadata will be assembled using a \"foreign\" name.  A \"foreign\" name al‐\nway ends with a digit string preceded by an underscore to differentiate  it  from  any\npossible local name. e.g.  /dev/md/11 or /dev/md/home0.\n\n\nHOMECLUSTER\nThe  homcluster line gives a default value for the --homecluster= option to mdadm.  It\nspecifies  the  cluster name for the md device.  The md device can be  assembled  only\non  the cluster which matches the name specified. If homcluster is not provided, mdadm\ntries to detect the cluster name automatically.\n\nThere should only be one homecluster line.  Any subsequent lines will be silently  ig‐\nnored.\n\n\nAUTO   A  list  of  names  of  metadata format can be given, each preceded by a plus or minus\nsign.  Also the word homehost is allowed as is all preceded by  plus  or  minus  sign.\nall is usually last.\n\nWhen  mdadm is auto-assembling an array, either via --assemble or --incremental and it\nfinds metadata of a given type, it checks that metadata type against those  listed  in\nthis  line.   The  first  match wins, where all matches anything.  If a match is found\nthat was preceded by a plus sign, the auto assembly is allowed.  If the match was pre‐\nceded by a minus sign, the auto assembly is disallowed.  If no  match  is  found,  the\nauto assembly is allowed.\n\nIf the metadata indicates that the array was created for this host, and the word home‐\nhost  appears  before  any other match, then the array is treated as a valid candidate\nfor auto-assembly.\n\nThis can be used to disable all auto-assembly (so that only arrays  explicitly  listed\nin mdadm.conf or on the command line are assembled), or to disable assembly of certain\nmetadata  types which might be handled by other software.  It can also be used to dis‐\nable assembly of all foreign arrays - normally such arrays are assembled but  given  a\nnon-deterministic name in /dev/md/.\n\nThe known metadata types are 0.90, 1.x, ddf, imsm.\n\nAUTO  should  be  given  at most once.  Subsequent lines are silently ignored.  Thus a\nlater config file in a config directory will not overwrite the setting in  an  earlier\nconfig file.\n\n\nPOLICY This  is used to specify what automatic behavior is allowed on devices newly appearing\nin the system and provides a way of marking spares that can be moved to  other  arrays\nas well as the migration domains.  Domain can be defined through policy line by speci‐\nfying  a  domain name for a number of paths from /dev/disk/by-path/.  A device may be‐\nlong to several domains. The domain of an array is a union of domains of  all  devices\nin  that  array.   A spare can be automatically moved from one array to another if the\nset of the destination array's domains contains all the domains of the new disk or  if\nboth arrays have the same spare-group.\n\nTo update hot plug configuration it is necessary to execute mdadm --udev-rules command\nafter changing the config file\n\nKeywords used in the POLICY line and supported values are:\n\n\ndomain=\nany arbitrary string\n\nmetadata=\n0.9 1.x ddf or imsm\n\npath=  file glob matching anything from /dev/disk/by-path\n\ntype=  either disk or part.\n\naction=\ninclude, re-add, spare, spare-same-slot, or force-spare\n\nauto=  yes, no, or homehost.\n\n\nThe  action  item determines the automatic behavior allowed for devices matching the path\nand type in the same line.  If a device matches several lines with different actions then\nthe most permissive will apply. The ordering of policy lines is irrelevant to the end re‐\nsult.\n\ninclude\nallows adding a disk to an array if metadata on that disk matches that array\n\nre-add will include the device in the array if it appears to be a  current  member  or  a\nmember  that was recently removed and the array has a write-intent-bitmap to allow\nthe re-add functionality.\n\nspare  as above and additionally: if the device is bare it can become a spare if there is\nany array that it is a candidate for based on domains and metadata.\n\nspare-same-slot\nas above and additionally if given slot was used by an array  that  went  degraded\nrecently  and  the device plugged in has no metadata then it will be automatically\nadded to that array (or it's container)\n\nforce-spare\nas above and the disk will become a spare in remaining cases\n\n\nPART-POLICY\nThis is similar to POLICY and accepts the same keyword assignments.  It allows a  con‐\nsistent set of policies to applied to each of the partitions of a device.\n\nA  PART-POLICY line should set type=disk and identify the path to one or more disk de‐\nvices.  Each partition on these disks will be treated according to the action= setting\nfrom this line.  If a domain is set in the line, then the domain associated with  each\npatition will be based on the domain, but with \"-partN\" appended, when N is the parti‐\ntion number for the partition that was found.\n\n\nSYSFS  The  SYSFS  line  lists  custom  values  of MD device's sysfs attributes which will be\nstored in sysfs after the array is assembled. Multiple lines are allowed and each line\nhas to contain the uuid or the name of the device to which it relates.  Lines are  ap‐\nplied in reverse order.\n\nuuid=  hexadecimal  identifier of MD device. This has to match the uuid stored in the su‐\nperblock.\n\nname=  name of the MD device as was given to mdadm when the array was created. It will be\nignored if uuid is not empty.\n\n\nMONITORDELAY\nThe monitordelay line gives a delay in seconds mdadm shall wait before pooling md  ar‐\nrays  when mdadm is running in --monitor mode.  -d/--delay command line argument takes\nprecedence over the config file.\n\nIf multiple MINITORDELAY lines are provided, only first non-zero value is considered.\n\n",
            "subsections": []
        },
        "FILES": {
            "content": "",
            "subsections": [
                {
                    "name": "/etc/mdadm.conf",
                    "content": "The default config file location, used when mdadm is running without --config option.\n\n"
                },
                {
                    "name": "/etc/mdadm.conf.d",
                    "content": "The default directory with config files. Used when mdadm is running without --config  option,\nafter  successful reading of the /etc/mdadm.conf default config file. Files in that directory\nare read in lexical order.\n\n\n"
                },
                {
                    "name": "/etc/mdadm/mdadm.conf",
                    "content": "Alternative config file that is read, when mdadm is running without --config option  and  the\n/etc/mdadm.conf default config file was not opened successfully.\n\n"
                },
                {
                    "name": "/etc/mdadm/mdadm.conf.d",
                    "content": "The alternative directory with config files. Used when mdadm is runninng without --config op‐\ntion, after reading the /etc/mdadm/mdadm.conf alternative config file whether it was success‐\nful or not. Files in that directory are read in lexical order.\n\n"
                }
            ]
        },
        "EXAMPLE": {
            "content": "DEVICE /dev/sd[bcdjkl]1\nDEVICE /dev/hda1 /dev/hdb1\n\n# /dev/md0 is known by its UUID.\nARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371\n# /dev/md1 contains all devices with a minor number of\n#   1 in the superblock.\nARRAY /dev/md1 superminor=1\n# /dev/md2 is made from precisely these two devices\nARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1\n\n# /dev/md4 and /dev/md5 are a spare-group and spares\n#  can be moved between them\nARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df\nspare-group=group1\nARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977\nspare-group=group1\n# /dev/md/home is created if need to be a partitionable md array\n# any spare device number is allocated.\nARRAY /dev/md/home UUID=9187a482:5dde19d9:eea3cc4a:d646ab8b\nauto=part\nPOLICY domain=domain1 metadata=imsm path=pci-0000:00:1f.2-scsi-*\naction=spare\nPOLICY domain=domain1 metadata=imsm path=pci-0000:04:00.0-scsi-[01]*\naction=include\n# One domain comprising of devices attached to specified paths is defined.\n# Bare device matching first path will be made an imsm spare on hot plug.\n# If more than one array is created on devices belonging to domain1 and\n# one of them becomes degraded, then any imsm spare matching any path for\n# given domain name can be migrated.\nMAILADDR root@mydomain.tld\nPROGRAM /usr/sbin/handle-mdadm-events\nCREATE group=system mode=0640 auto=part-8\nHOMEHOST <system>\nAUTO +1.x homehost -all\nSYSFS name=/dev/md/raid5 groupthreadcnt=4 syncspeedmax=1000000\nSYSFS uuid=bead5eb6:31c17a27:da120ba2:7dfda40d groupthreadcnt=4 syncspeedmax=1000000\nMONITORDELAY 60\n\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "mdadm(8), md(4).\n\nMDADM.CONF(5)",
            "subsections": []
        }
    },
    "summary": "mdadm.conf - configuration for management of Software RAID with mdadm",
    "flags": [],
    "examples": [
        "DEVICE /dev/sd[bcdjkl]1",
        "DEVICE /dev/hda1 /dev/hdb1",
        "# /dev/md0 is known by its UUID.",
        "ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371",
        "# /dev/md1 contains all devices with a minor number of",
        "#   1 in the superblock.",
        "ARRAY /dev/md1 superminor=1",
        "# /dev/md2 is made from precisely these two devices",
        "ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1",
        "# /dev/md4 and /dev/md5 are a spare-group and spares",
        "#  can be moved between them",
        "ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df",
        "spare-group=group1",
        "ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977",
        "spare-group=group1",
        "# /dev/md/home is created if need to be a partitionable md array",
        "# any spare device number is allocated.",
        "ARRAY /dev/md/home UUID=9187a482:5dde19d9:eea3cc4a:d646ab8b",
        "auto=part",
        "POLICY domain=domain1 metadata=imsm path=pci-0000:00:1f.2-scsi-*",
        "action=spare",
        "POLICY domain=domain1 metadata=imsm path=pci-0000:04:00.0-scsi-[01]*",
        "action=include",
        "# One domain comprising of devices attached to specified paths is defined.",
        "# Bare device matching first path will be made an imsm spare on hot plug.",
        "# If more than one array is created on devices belonging to domain1 and",
        "# one of them becomes degraded, then any imsm spare matching any path for",
        "# given domain name can be migrated.",
        "MAILADDR root@mydomain.tld",
        "PROGRAM /usr/sbin/handle-mdadm-events",
        "CREATE group=system mode=0640 auto=part-8",
        "HOMEHOST <system>",
        "AUTO +1.x homehost -all",
        "SYSFS name=/dev/md/raid5 groupthreadcnt=4 syncspeedmax=1000000",
        "SYSFS uuid=bead5eb6:31c17a27:da120ba2:7dfda40d groupthreadcnt=4 syncspeedmax=1000000",
        "MONITORDELAY 60"
    ],
    "see_also": [
        {
            "name": "mdadm",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/mdadm/8/json"
        },
        {
            "name": "md",
            "section": "4",
            "url": "https://www.chedong.com/phpMan.php/man/md/4/json"
        }
    ]
}