8A0A(B BBBF LM # ( `M ; FDD fDB M # M ԋ ( M Ќ FAC |
ABG @ M D FBE A(C0D@G
0D(A BBBI H $N FEE E(D0A8D@:
8A0A(B BBBF $ pN T EAG DAAH N < FJB B(D0A8G@]
8A0A(B BBBI 0 N e E(
C H
H H
H H
A K ( O ̖( EAD0
AAE \ DO З* FBE E(I0D8L_
8D0A(B BBBI qJ`A H O FEH B(A0D8D`
8D0A(B BBBD 4 O $] FDA m
ABE PAK (P LV H
8A0A(B BBBA ( ` - ECJ
AAA ( ,` . FCJk
ABA \ X` . FDB B(A0A8J
7
I
W
A
q
8A0A(B BBBA 4 ` L0C FAD G'
AABA ` d1` FKB B(A0A8D`hEpThA`hDpIxGI`
8A0A(B BBBF
8F0A(B BBBM L ta @: FBB B(A0D8D
8D0A(B BBBJ X a =u FDB B(A0D8Dp
8D0A(B BBBA 2xNYxAp *
8 4b CG BBA A(D@
(A ABBH H pb E] BBA A(D0{
(A ABBE D(C ABB b E' L b F FBA A(D0
(A ABBH ~
(C ABBA d c G FBB B(A0D8DPS
8C0A(B BBBD -
8A0A(B BBBI < c I FBA A(GC
(A ABBF X c J FEB E(A0E8D`s
8A0A(B BBBG hMpYhA` \ $d `M FBB B(A0A8D-
8D0A(B BBBD 5
\`B t d Z FEB B(D0A8G6
8D0A(B BBBB [aBK`A d a e b $e b; 8e Lb
Le HbG `e bU te b , e bk KDA OABF 4 e c FAA
ABH DAE e c BBB B(A0K8D`hCpQhV`hFpExITBAFHFDDI`r8C0H(G BBB D xf e BBB B(A0A8DPi8D0A(B BBB4 f f2 BBA G L#J
ABBI f g? Tj g 4ga $g g5 Ao @g gM B}
A P \g g MBG I(A0D8FP
8A0A(B BBBE pH g h FHB B(A0H8Kpc
8D0A(B BBBJ 8 g (j FBD A(G
(A ABBA 8h j{ @s Ph dk H dh 0ll FBB E(A0A8DP
8D0A(B BBBF 0 h Tm BDC D@
AABE H h n BEA A(G0T
(D ABBC D(D DBB H 0i dn$ BBB B(A0A8DPr
8C0A(B BBBD L |i Ho BEL B(A0A8G
8D0A(B BBBA i p BKB B(A0I8D`hCpQhV`hIpFxEPFAFHFDDI`x
8A0H(G DBBO ` Xj \s FBA A(D0
(A ABBD
(A ABBA O
(F ABBE zR x 0 $ e
, j u FAG L!
DBA ( k v BLP@e
DBA H Lk w FBB A(A0G I
0D(A BBBK k Lx k Xy k y
k yG , k ,z2 BAC
ABF l <{# A] 4l P{ EZ L Pl T{ BJE A(D0t
(D BBBD |(A BBB ( l |A EDL aAAH H l } BBB E(D0D8DP
8D0A(B BBBE m ~{ AD G
AC ( H } BBB B(A0A8D`
8A0A(B BBBA
L } P FBB E(A0A8D
8D0A(B BBBA N
H X~ FBB B(A0A8DPE
8D0A(B BBBD ` ~ !l FBE B(A0A8D`
8A0A(B BBBF l
8A0A(B BBBE H $ FDB B(A0D8Gs
8D0A(B BBBF $ zR x ,
( `' FCJk
ABA ( ' FCJk
ABA 0 (( FCD G
AABA H 0 (Z FBB B(A0A8G
8A0A(B BBBB ( | ) FAG}
ABB L L* FBB B(A0A8G
8A0A(B BBBH $ zR x , ( 4 5 FA
BF DE , ` $6R AC
HK
K TB L `B BBB B(A0A8Q`
8D0A(B BBBH H F BEE B(A0A8Dz
8D0A(B BBBE H @ I BBA A(D0W
(C ABBG G
(D ABBH d I; BBB B(A0A8D`ghWpIhA`
8D0A(B BBBH mhNpYhD` | Nn FBE B(A0A8DpsxYDBIp[
8D0A(B BBBH rx]GxBp7xGDBVp H t U FBB E(A0F8FP
8D0A(B BBBI X H ԃ X FBB E(D0D8DP
8A0A(B BBBH L tY FEB B(A0A8Dm
8A0A(B BBBA $ zR x , 2( ` Z FBB E(A0A8G` hNpMxBBBI`o
8D0A(B BBBG 4 4\x FBD D(G0Z(A ABBH H |\f FOH B(A0F8Gm
8D0A(B BBBI \ `5 FBB B(A0A8GJOA
8D0A(B BBBH |
h lf FGB E(A0D8GWHNBBBNE
8A0A(B BBBH H t l FBD A(G0X
(C ABBD d(C ABB L TmT FIE B(E0G8G
8D0A(B BBBC
L $ Ps FOB G(D0A8G
8D0A(B BBBE 8 t ua FBF D(P
(A ABBG h Tv FBB B(A0A8G
8D0A(B BBBF MAABBb @ { BBE A(D0Jp
0D(A BBBE H ` d} BGB B(I0C8Dp[
8D0A(B BBBK \ FBB B(D0A8J<PKA
8D0A(B BBBG L % FBE E(D0A8J
8D0A(B BBBE < \ FBG F(IA
(D BBBG H0 Hg ` EU Љ dc cv @ x FBE A(C0G@v
0D(A BBBG @ , a FGB A(H0G@[
0D(A BBBK p $~ , k FQC p
ABC А0 Hg ̊ EU l EV
E KH FBB B(A0A8G L@LC\CTCFCFCPC|
8A0A(B BBBA 0 FDA G
AABA H 9 FEE E(D0D8D`
8D0A(B BBBA 4 @ r FDA Q
ABA NAB x 2 Q` 4 @s FAA s
ABB V
AED 4 ̘ s FAA o
ABF V
AED < FAA U
ABH ]
AEE D @ X < , l H EMO
AAD H BBB B(A0A8G
8A0A(B BBBD H l BBB B(A0A8G
8A0A(B BBBD 0 4 @ FKC G0P
AABA 8 h FDI C(G@
(A ABBI R H@D
A a HP|
D < ܚ ({ FSK A(G
(D ABBD h FG@h
EF ( @ @ FAD `
DBG 0 l FAA Dpw
DABF ( FRNpR
ABA 0 ̛ FAA GPs
AABJ L FBB B(D0D8D
8D0A(B BBBK \ P / FBB G(A0F8D@
8D0A(B BBBJ [8H0O(B BBB( FADPm
DBB ܜ EL ] EK
A <] EK
A 4 ] EK
A P ] EK
A $ l F AAD }AA 4 0 ADD \
AAI DAA 4 ̝ m BCC b
ABC Z
ABA , + AC
BEED
A 0 4 NAG |CAJH 4 h w BBB B(A0A8G L!Q!K!K!K"F"K"K"I"D"H"K"K"J"A"K!P!N!c!B!i
8A0A(B BBBF !A!A!E"A"G"A"B"B"H"J"H"I"A"K!H!S!^!A!!E!E!E"E"E"E"B"H"E"E"H"B"H"S!H!S!`!A! ( ( L FHA yAB ( 4 EC
G
E ( FBB B(A0A8G L@IAAKAlABATAMAVAAAI
8A0A(B BBBH wALAUAAA (
ECD
AAC Ġ C ؠ C ( FGLP
DBI 0 FAK DPI
AABE L ED@O
AG @ p Db FAG w
DBE
DBE D
DBE p EmPO
AA ء y K^
G 0 @p FKG R
ABC yDB $ ( |< FDD gDB $ P < FDD gDB P x 6 FBB B(A0A8G I
8A0A(B BBBD ̢ T MF [i
D RF , hs PAD RABF \ L bPH A(
ABBA @H(C
ABBH > D> ԣ pE D e FIE E(D0H8G@n8A0A(B BBB 4 P ? !? (? 0? 6? C? O? [? ` d i n u h: m f `
h 0 8 o
X hF P+ o o 8 o o o 0` @` P` `` p` ` ` ` ` ` ` ` ` a a a 0a @a Pa `a pa a a a a a a a a b b b 0b @b Pb `b pb b b b b b b b b c c c 0c @c Pc `c pc c c c c c c c c d d d 0d @d Pd `d pd d d d d d d d d e e e 0e @e Pe `e pe e e e e e e e e f f f 0f @f Pf `f pf f f f f f f f f g g g 0g @g Pg `g pg g g g g g g g g h h h 0h @h Ph `h ph h h h h h h h h i i i 0i @i Pi `i pi i i i i homehost no yes /etc/mdadm.conf.d /etc/mdadm.conf /etc/mdadm/mdadm.conf.d /etc/mdadm/mdadm.conf 8@ B i
$ D + 1 < 7 # do not edit this file, it is automatically generated by mdadm
auto domain action metadata part-policy policy type path disk part The /etc/mdadm/mdadm.conf config file:
The config file contains, apart from blank lines and comment lines that
start with a hash(#), array lines, device lines, and various
configuration lines.
Each line is constructed of a number of space separated words, and can
be continued on subsequent physical lines by indenting those lines.
A device line starts with the word 'device' and then has a number of words
which identify devices. These words should be names of devices in the
filesystem, and can contain wildcards. There can be multiple words or each
device line, and multiple device lines. All devices so listed are checked
for relevant super blocks when assembling arrays.
An array line start with the word 'array'. This is followed by the name of
the array device in the filesystem, e.g. '/dev/md2'. Subsequent words
describe the identity of the array, used to recognise devices to include in the
array. The identity can be given as a UUID with a word starting 'uuid=', or
as a minor-number stored in the superblock using 'super-minor=', or as a list
of devices. This is given as a comma separated list of names, possibly
containing wildcards, preceded by 'devices='. If multiple critea are given,
than a device must match all of them to be considered.
Other configuration lines include:
mailaddr, mailfrom, program used for --monitor mode
create, auto used when creating device names in /dev
homehost, policy, part-policy used to guide policy in various
situations
Usage: mdadm --incremental [-Rqrsf] device
This usage allows for incremental assembly of md arrays. Devices can be
added one at a time as they are discovered. Once an array has all expected
devices, it will be started.
Optionally, the process can be reversed by using the fail option.
When fail mode is invoked, mdadm will see if the device belongs to an array
and then both fail (if needed) and remove the device from that array.
Options that are valid with incremental assembly (-I --incremental) are:
--run -R : Run arrays as soon as a minimal number of devices are
: present rather than waiting for all expected.
--quiet -q : Don't print any information messages, just errors.
--rebuild-map -r : Rebuild the 'map' file that mdadm uses for tracking
: partial arrays.
--scan -s : Use with -R to start any arrays that have the minimal
: required number of devices, but are not yet started.
--fail -f : First fail (if needed) and then remove device from
: any array that it is a member of.
Usage: mdadm --grow device options
This usage causes mdadm to attempt to reconfigure a running array.
This is only possibly if the kernel being used supports a particular
reconfiguration.
Options that are valid with the grow (-G --grow) mode are:
--level= -l : Tell mdadm what level to convert the array to.
--layout= -p : For a FAULTY array, set/change the error mode.
: for other arrays, update the layout
--size= -z : Change the active size of devices in an array.
: This is useful if all devices have been replaced
: with larger devices. Value is in Kilobytes, or
: the special word 'max' meaning 'as large as possible'.
--assume-clean : When increasing the --size, this flag will avoid
: a resync of the new space
--chunk= -c : Change the chunksize of the array
--raid-devices= -n : Change the number of active devices in an array.
--add= -a : Add listed devices as part of reshape. This is
: needed for resizing a RAID0 which cannot have
: spares already present.
--bitmap= -b : Add or remove a write-intent bitmap.
--backup-file= file : A file on a different device to store data for a
: short time while increasing raid-devices on a
: RAID4/5/6 array. Also needed throughout a reshape
: when changing parameters other than raid-devices
--array-size= -Z : Change visible size of array. This does not change any
: data on the device, and is not stable across restarts.
--data-offset= : Location on device to move start of data to.
--consistency-policy= : Change the consistency policy of an active array.
-k : Currently works only for PPL with RAID5.
Usage: mdadm --monitor options devices
This usage causes mdadm to monitor a number of md arrays by periodically
polling their status and acting on any changes.
If any devices are listed then those devices are monitored, otherwise
all devices listed in the config file are monitored.
The address for mailing advisories to, and the program to handle
each change can be specified in the config file or on the command line.
There must be at least one destination for advisories, whether
an email address, a program, or --syslog
Options that are valid with the monitor (-F --follow) mode are:
--mail= -m : Address to mail alerts of failure to
--program= -p : Program to run when an event is detected
--alert= : same as --program
--syslog -y : Report alerts via syslog
--increment= -r : Report RebuildNN events in the given increment. default=20
--delay= -d : seconds of delay between polling state. default=60
--config= -c : specify a different config file
--scan -s : find mail-address/program in config file
--daemonise -f : Fork and continue in child, parent exits
--pid-file= -i : In daemon mode write pid to specified file instead of stdout
--oneshot -1 : Check for degraded arrays, then exit
--test -t : Generate a TestMessage event against each array at startup
Usage: mdadm misc_option devices...
This usage is for performing some task on one or more devices, which
may be arrays or components, depending on the task.
The --misc option is not needed (though it is allowed) and is assumed
if the first argument in a misc option.
Options that are valid with the miscellaneous mode are:
--query -Q : Display general information about how a
device relates to the md driver
--detail -D : Display details of an array
--detail-platform : Display hardware/firmware details
--examine -E : Examine superblock on an array component
--examine-bitmap -X: Display contents of a bitmap file
--examine-badblocks: Display list of known bad blocks on device
--zero-superblock : erase the MD superblock from a device.
--run -R : start a partially built array
--stop -S : deactivate array, releasing all resources
--readonly -o : mark array as readonly
--readwrite -w : mark array as readwrite
--test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing
--wait -W : wait for resync/rebuild/recovery to finish
--action= : initiate or abort ('idle' or 'frozen') a 'check' or 'repair'.
Usage: mdadm arraydevice options component devices...
This usage is for managing the component devices within an array.
The --manage option is not needed and is assumed if the first argument
is a device name or a management option.
The first device listed will be taken to be an md array device, any
subsequent devices are (potential) components of that array.
Options that are valid with management mode are:
--add -a : hotadd subsequent devices to the array
--re-add : subsequent devices are re-added if there were
: recent members of the array
--remove -r : remove subsequent devices, which must not be active
--fail -f : mark subsequent devices a faulty
--set-faulty : same as --fail
--replace : mark device(s) to be replaced by spares. Once
: replacement completes, device will be marked faulty
--with : Indicate which spare a previous '--replace' should
: prefer to use
--run -R : start a partially built array
--stop -S : deactivate array, releasing all resources
--readonly -o : mark array as readonly
--readwrite -w : mark array as readwrite
Usage: mdadm --assemble device options...
mdadm --assemble --scan options...
This usage assembles one or more raid arrays from pre-existing
components.
For each array, mdadm needs to know the md device, the identity of
the array, and a number of sub devices. These can be found in a number
of ways.
The md device is given on the command line, is found listed in the
config file, or can be deduced from the array identity.
The array identity is determined either from the --uuid, --name, or
--super-minor commandline arguments, from the config file,
or from the first component device on the command line.
The different combinations of these are as follows:
If the --scan option is not given, then only devices and identities
listed on the command line are considered.
The first device will be the array device, and the remainder will be
examined when looking for components.
If an explicit identity is given with --uuid or --super-minor, then
only devices with a superblock which matches that identity is considered,
otherwise every device listed is considered.
If the --scan option is given, and no devices are listed, then
every array listed in the config file is considered for assembly.
The identity of candidate devices are determined from the config file.
After these arrays are assembled, mdadm will look for other devices
that could form further arrays and tries to assemble them. This can
be disabled using the 'AUTO' option in the config file.
If the --scan option is given as well as one or more devices, then
Those devices are md devices that are to be assembled. Their identity
and components are determined from the config file.
If mdadm can not find all of the components for an array, it will assemble
it but not activate it unless --run or --scan is given. To preserve this
behaviour even with --scan, add --no-degraded. Note that "all of the
components" means as many as were present the last time the array was running
as recorded in the superblock. If the array was already degraded, and
the missing device is not a new problem, it will still be assembled. It
is only newly missing devices that cause the array not to be started.
Options that are valid with --assemble (-A) are:
--bitmap= : bitmap file to use with the array
--uuid= -u : uuid of array to assemble. Devices which don't
have this uuid are excluded
--super-minor= -m : minor number to look for in super-block when
choosing devices to use.
--name= -N : Array name to look for in super-block.
--config= -c : config file
--scan -s : scan config file for missing information
--run -R : Try to start the array even if not enough devices
for a full array are present
--force -f : Assemble the array even if some superblocks appear
: out-of-date. This involves modifying the superblocks.
--update= -U : Update superblock: try '-A --update=?' for option list.
--no-degraded : Assemble but do not start degraded arrays.
--readonly -o : Mark the array as read-only. No resync will start.
Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices
This usage is similar to --create. The difference is that it creates
a legacy array without a superblock. With these arrays there is no
different between initially creating the array and subsequently
assembling the array, except that hopefully there is useful data
there in the second case.
The level may only be 0, 1, 10, linear, multipath, or faulty.
All devices must be listed and the array will be started once complete.
Options that are valid with --build (-B) are:
--bitmap= : file to store/find bitmap information in.
--chunk= -c : chunk size of kibibytes
--rounding= : rounding factor for linear array (==chunk size)
--level= -l : 0, 1, 10, linear, multipath, faulty
--raid-devices= -n : number of active devices in array
--bitmap-chunk= : bitmap chunksize in Kilobytes.
--delay= -d : bitmap update delay in seconds.
Usage: mdadm --create device --chunk=X --level=Y --raid-devices=Z devices
This usage will initialise a new md array, associate some
devices with it, and activate the array. In order to create an
array with some devices missing, use the special word 'missing' in
place of the relevant device name.
Before devices are added, they are checked to see if they already contain
raid superblocks or filesystems. They are also checked to see if
the variance in device size exceeds 1%.
If any discrepancy is found, the user will be prompted for confirmation
before the array is created. The presence of a '--run' can override this
caution.
If the --size option is given then only that many kilobytes of each
device is used, no matter how big each device is.
If no --size is given, the apparent size of the smallest drive given
is used for raid level 1 and greater, and the full device is used for
other levels.
Options that are valid with --create (-C) are:
--bitmap= -b : Create a bitmap for the array with the given filename
: or an internal bitmap if 'internal' is given
--chunk= -c : chunk size in kibibytes
--rounding= : rounding factor for linear array (==chunk size)
--level= -l : raid level: 0,1,4,5,6,10,linear,multipath and synonyms
--parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric
--layout= : same as --parity, for RAID10: [fno]NN
--raid-devices= -n : number of active devices in array
--spare-devices= -x : number of spare (eXtra) devices in initial array
--size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional
--data-offset= : Space to leave between start of device and start
: of array data.
--force -f : Honour devices as listed on command line. Don't
: insert a missing drive for RAID5.
--run -R : insist of running the array even if not all
: devices are present or some look odd.
--readonly -o : start the array readonly - not supported yet.
--name= -N : Textual name for array - max 32 characters
--bitmap-chunk= : bitmap chunksize in Kilobytes.
--delay= -d : bitmap update delay in seconds.
--write-journal= : Specify journal device for RAID-4/5/6 array
--consistency-policy= : Specify the policy that determines how the array
-k : maintains consistency in case of unexpected shutdown.
Any parameter that does not start with '-' is treated as a device name
or, for --examine-bitmap, a file name.
The first such name is often the name of an md device. Subsequent
names are often names of component devices.
Some common options are:
--help -h : General help message or, after above option,
mode specific help message
--help-options : This help message
--version -V : Print version information for mdadm
--verbose -v : Be more verbose about what is happening
--quiet -q : Don't print un-necessary messages
--brief -b : Be less verbose, more brief
--export -Y : With --detail, --detail-platform or --examine use
key=value format for easy import into environment
--force -f : Override normal checks and be more forceful
--assemble -A : Assemble an array
--build -B : Build an array without metadata
--create -C : Create a new array
--detail -D : Display details of an array
--examine -E : Examine superblock on an array component
--examine-bitmap -X: Display the detail of a bitmap file
--examine-badblocks: Display list of known bad blocks on device
--monitor -F : monitor (follow) some arrays
--grow -G : resize/ reshape and array
--incremental -I : add/remove a single device to/from an array as appropriate
--query -Q : Display general information about how a
device relates to the md driver
--auto-detect : Start arrays auto-detected by the kernel
mdadm is used for building, managing, and monitoring
Linux md devices (aka RAID arrays)
Usage: mdadm --create device options...
Create a new array from unused devices.
mdadm --assemble device options...
Assemble a previously created array.
mdadm --build device options...
Create or assemble an array without metadata.
mdadm --manage device options...
make changes to an existing array.
mdadm --misc options... devices
report on or modify various md related devices.
mdadm --grow options device
resize/reshape an active array
mdadm --incremental device
add/remove a device to/from an array as appropriate
mdadm --monitor options...
Monitor one or more array for significant changes.
mdadm device options...
Shorthand for --manage.
Any parameter that does not start with '-' is treated as a device name
or, for --examine-bitmap, a file name.
The first such name is often the name of an md device. Subsequent
names are often names of component devices.
For detailed help on the above major modes use --help after the mode
e.g.
mdadm --assemble --help
For general help on options use
mdadm --help-options
Usage: mdadm --help
for help
-ABCDEFGIQhVXYWZ:vqb:c:i:l:p:m:n:x:u:c:d:z:U:N:sa:rfRSow1tye:k: -ABCDEFGIQhVXYWZ:vqb:c:i:l:p:m:n:x:u:c:d:z:U:N:sarfRSow1tye:k: -ABCDEFGIQhVXYWZ:vqbc:i:l:p:m:n:x:u:c:d:z:U:N:sarfRSow1tye:k: mdadm - v4.1 - 2018-10-01
` @ n ? u G z A ? B $ C D E F G I ^ Q X 6 8 9 : Y \ ` . a 3 b ; F h C = U V P v X q J ^ J g l m N pj N t n n x x 2 z 1 O , e V - . K > L M / D 3 5 _ Z d M e g k ? u " Q _ N I s P i U Z @ / A 9 B E C L D Q D \ E d F i R m S r o { w 0 H 7 = c f > Y 1 t ] R S S T i d U U 1 i y < 2 X , Z s [ 7 W ~ ; . 0 2 6 8 : > @= " r , 6 D
< 2 8 % K [ ^ m ~ 2 z ? $ n u ;
! y 6
> : ti
, / 2 5 B N _ m
|
, / 2 5 B N _ m /run/mdadm/creating-%s @= r , D p @ p p 0 p 0 p ` 0 0 " @ 0 p p ` - @ @( p ` Linux-MD @ J `O ` P M 0x I Y v { `J 8 B Ѕ 0V @ G _ ^ L T ] d l r x ~ % ʨ ި ; ) 9 1 C C /dev/disk/by-path/ P @ ` 3 0 ( ` ` { ` @ P q 0o `k p ` @_ @ `{ D 0 # P" $ p p @ t # " $ 0 B B i i A P c ffe3c6cf318e21e53c24fab067cc8441bbe40f.debug G .shstrtab .interp .note.gnu.property .note.gnu.build-id .note.ABI-tag .gnu.hash .dynsym .dynstr .gnu.version .gnu.version_r .rela.dyn .rela.plt .init .plt.got .plt.sec .text .fini .rodata .eh_frame_hdr .eh_frame .init_array .fini_array .data.rel.ro .dynamic .data .bss .gnu_debuglink 8 8 & X X $ 9 | | G o 8 Q H Y a o F n o 8 8 } P+ B hF hF X ` ` ` ` i i i i `s `s L h h
- X X H 0 0 8 8 @ @ m @ - U - 4 -