[thirdparty/mdadm.git] / mdadm.conf-example

# 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
Commit	Line	Data
56eb10c0 NB	1	# mdadm configuration file
	2	#
	3	# mdadm will function properly without the use of a configuration file,
	4	# but this file is useful for keeping track of arrays and member disks.
	5	# In general, a mdadm.conf file is created, and updated, after arrays
	6	# are created. This is the opposite behavior of /etc/raidtab which is
	7	# created prior to array construction.
	8	#
	9	#
	10	# the config file takes two types of lines:
	11	#
	12	# DEVICE lines specify a list of devices of where to look for
	13	# potential member disks
	14	#
	15	# ARRAY lines specify information about how to identify arrays so
	16	# so that they can be activated
	17	#
	18	# You can have more than one device line and use wild cards. The first
	19	# example includes SCSI the first partition of SCSI disks /dev/sdb,
	20	# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
	21	# line looks for array slices on IDE disks.
	22	#
	23	#DEVICE /dev/sd[bcdjkl]1
	24	#DEVICE /dev/hda1 /dev/hdb1
	25	#
	26	#
	27	#
	28	# ARRAY lines specify an array to assemble and a method of identification.
	29	# Arrays can currently be identified by using a UUID, superblock minor number,
	30	# or a listing of devices.
	31	#
	32	# super-minor is usally the minor number of the metadevice
	33	# UUID is the Universally Unique Identifier for the array
	34	# Each can be obtained using
	35	#
	36	# mdadm -D <md>
	37	#
	38	#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
	39	#ARRAY /dev/md1 superminor=1
	40	#ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2