41 lines
1.4 KiB
Plaintext
41 lines
1.4 KiB
Plaintext
|
# mdadm configuration file
|
||
|
|
#
|
||
|
|
# mdadm will function properly without the use of a configuration file,
|
||
|
|
# but this file is useful for keeping track of arrays and member disks.
|
||
|
|
# In general, a mdadm.conf file is created, and updated, after arrays
|
||
|
|
# are created. This is the opposite behavior of /etc/raidtab which is
|
||
|
|
# created prior to array construction.
|
||
|
|
#
|
||
|
|
#
|
||
|
|
# the config file takes two types of lines:
|
||
|
|
#
|
||
|
|
# DEVICE lines specify a list of devices of where to look for
|
||
|
|
# potential member disks
|
||
|
|
#
|
||
|
|
# ARRAY lines specify information about how to identify arrays so
|
||
|
|
# so that they can be activated
|
||
|
|
#
|
||
|
|
# You can have more than one device line and use wild cards. The first
|
||
|
|
# example includes SCSI the first partition of SCSI disks /dev/sdb,
|
||
|
|
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
|
||
|
|
# line looks for array slices on IDE disks.
|
||
|
|
#
|
||
|
|
#DEVICE /dev/sd[bcdjkl]1
|
||
|
|
#DEVICE /dev/hda1 /dev/hdb1
|
||
|
|
#
|
||
|
|
#
|
||
|
|
#
|
||
|
|
# ARRAY lines specify an array to assemble and a method of identification.
|
||
|
|
# Arrays can currently be identified by using a UUID, superblock minor number,
|
||
|
|
# or a listing of devices.
|
||
|
|
#
|
||
|
|
# super-minor is usally the minor number of the metadevice
|
||
|
|
# UUID is the Universally Unique Identifier for the array
|
||
|
|
# Each can be obtained using
|
||
|
|
#
|
||
|
|
# mdadm -D <md>
|
||
|
|
#
|
||
|
|
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
|
||
|
|
#ARRAY /dev/md1 superminor=1
|
||
|
|
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2
|