2002-03-15 06:21:36 +01:00
|
|
|
.TH MDADM.CONF 5
|
|
|
|
.SH NAME
|
|
|
|
mdadm.conf \- configuration for management of Software Raid with mdadm
|
|
|
|
.SH SYNOPSIS
|
|
|
|
/etc/mdadm.conf
|
|
|
|
.SH DESCRIPTION
|
|
|
|
.PP
|
|
|
|
.B mdadm
|
2002-03-20 23:39:50 +01:00
|
|
|
is a tool for creating, managing, and monitoring RAID devices using the
|
2002-03-15 06:21:36 +01:00
|
|
|
.B md
|
|
|
|
driver in Linux.
|
|
|
|
.PP
|
|
|
|
Some common tasks, such as assembling all arrays, can be simplified
|
2002-03-20 23:39:50 +01:00
|
|
|
by describing the devices and array in this configuation file.
|
2002-03-15 06:21:36 +01:00
|
|
|
|
|
|
|
.SS SYNTAX
|
|
|
|
The file should be seen as a collection of words separated by white
|
|
|
|
space (space, tab, or newline).
|
2002-03-20 23:39:50 +01:00
|
|
|
Any word that beings with a hash sign (#) starts a comment and that
|
2002-03-15 06:21:36 +01:00
|
|
|
word together with the remainder of the line are ignored.
|
|
|
|
|
|
|
|
Any line that start with white space (space or tab) is treated as
|
|
|
|
though it were a continuation of the previous line.
|
|
|
|
|
|
|
|
Empty lines are ignored, but otherwise each (non continuation) line
|
|
|
|
must start with a keyword as listed below. The key words are case
|
|
|
|
insensitve and can be abbreviated to 3 characters.
|
|
|
|
|
|
|
|
The keywords are:
|
|
|
|
.TP
|
|
|
|
.B DEVICE
|
|
|
|
A
|
|
|
|
.B device
|
|
|
|
line lists the devices (whole devices or partitions) that might contain
|
|
|
|
a component of an MD array. When looking for the components of an
|
|
|
|
array,
|
|
|
|
.B mdadm
|
|
|
|
will scan these devices and no others.
|
|
|
|
|
|
|
|
The
|
|
|
|
.B device
|
|
|
|
line may contain a number of different devices (separated by spaces)
|
|
|
|
and each device name can contain wild cards as defined by
|
|
|
|
.BR glob (7).
|
|
|
|
|
|
|
|
Also, there may be several device lines present in the file.
|
|
|
|
|
2002-03-20 23:39:50 +01:00
|
|
|
For example:
|
|
|
|
.IP
|
|
|
|
DEVICE /dev/hda* /dev/hdc*
|
|
|
|
.br
|
|
|
|
DEV /dev/sd*
|
|
|
|
.br
|
|
|
|
DEVICE /dev/discs/disc*/disc
|
|
|
|
|
2002-03-15 06:21:36 +01:00
|
|
|
.TP
|
|
|
|
.B ARRAY
|
2002-03-20 23:39:50 +01:00
|
|
|
The ARRAY lines identify actual arrays. The second word on the line
|
|
|
|
should be the name of the device where the array is normally
|
|
|
|
assembled, such as
|
|
|
|
.BR /dev/md1 .
|
|
|
|
Subsequent words identify the array. If multiple identities are given,
|
|
|
|
then the array must match ALL identities to be considered a match.
|
|
|
|
Each identity word has a tag, and equals sign, and some value.
|
|
|
|
The options are:
|
|
|
|
|
|
|
|
.RS 4
|
|
|
|
.TP
|
|
|
|
.B uuid=
|
|
|
|
The value should be a 128 bit uuid in hexadecimal, with punctuation
|
|
|
|
interspersed if desired. This must match the uuid stored in the
|
|
|
|
superblock.
|
|
|
|
.TP
|
|
|
|
.B super-minor=
|
|
|
|
The value is an integer which indicates the minor number that was
|
|
|
|
stored in the superblock when the array was created. When an array is
|
|
|
|
created as /dev/mdX, then the minor number X is stored.
|
|
|
|
.TP
|
|
|
|
.B devices=
|
|
|
|
The value is a comma separated list of device names. Precisely these
|
|
|
|
devices will be used to assemble the array. Note that the devices
|
|
|
|
listed there must also be listed on a DEVICE line.
|
|
|
|
.TP
|
|
|
|
.B level=
|
|
|
|
The value is a raid level. This is not normally used to
|
|
|
|
identify an array, but is supported so that the output of
|
|
|
|
|
|
|
|
.B "mdadm --examine --scan"
|
|
|
|
|
|
|
|
can be use directly in the configuration file.
|
|
|
|
.TP
|
|
|
|
.B disks=
|
|
|
|
The value is the number of disks in a complete active array. As with
|
|
|
|
.B level=
|
|
|
|
this is mainly for compatibility with the output of
|
2002-03-15 06:21:36 +01:00
|
|
|
|
2002-03-20 23:39:50 +01:00
|
|
|
.BR "mdadm --examine --scan" .
|
|
|
|
.RE
|
2002-03-15 06:21:36 +01:00
|
|
|
.SH SEE ALSO
|
2002-03-20 23:39:50 +01:00
|
|
|
.BR mdadm (8),
|
|
|
|
.BR md (4).
|
2002-03-15 06:21:36 +01:00
|
|
|
|