[thirdparty/mdadm.git] / ChangeLog
1Changed Prior to 0.8 release
2 - update mdadm.spec
3 - use BLKGETSIZE64 if available for array size
4 - give human readable as GiB/MiB and GB and MB, with 2 decimal point precision
5 - Only warn about size variation for raid1/4/5.
6 - Started md.4 man page
7 - Started mdadm.conf.5 man page
9Changes Prior to 0.7 release
11 - Fix makefile to install binary at /sbin and not /sbin/sbin
12 Also install man page.
13 - Add --zero-superblock based on --destroywithextremeprejudice
14 from Dale Stephenson <>
15 - change name to mdadm. It is palandromic, and much nicer to pronouce.
17Changes Prior to 0.6 release
9a9dab36 19 - Remove the limit on the number of device names that can be
20 given on the command line.
21 - Fix bug in --assemble --force where it would only update a
22 single superblock.
23 - Fix bogus printing of big numbers not being block devices
24 when given names of devices that don't exist.
25 - When --assemble --force, consider superblocks with an event
26 count that is 1 behind as out-of-date. Normally they are
27 considered up-to-date (as the kernel assumes this too).
28 - When marking drives as not-failed in the superblock,
29 we also mark them as ACTIVE and SYNC.
30 - Don't start arrays for which not all drives are available unless:
31 --scan which implies that all drives were found automatically
32 --run which means the user knows what they want
33 --force which means that we are fixing something broken
34 - Make sure all device numbers passed as 3rd arg of ioctl
35 are passed as unsigned lock, so that it works on SPARC
36 - If HOT_ADD_DISK failes for -a, then only try ADD_NEW_DISK
37 if we cannot read from the array, i.e. if the array is
38 not started yet.
39 - man page update
40 - Taught Examine to handle --scan. It examines all devices listed
41 on DEVICE lines in the config file.
42 - Added --brief (-b) flag for Examine and Detail to print out
43 and mdctl.conf compatible description with uuid=, level=,
44 disks= and - for Examine - devices=
45 --examine --brief collects all devices the make the one array and
46 list them as one entry.
47 - Added level= and disks= options to ARRAY lines in config files
48 so --brief output could be used as-is.
49 - Make parity style ({left,right}-{,a}symmetric) consistantly use -,
50 never _.
51 - Add "Array Size" to --detail output
52 - Change "Size" to "Device Size" and exclude from Detail of arrays
53 that do not have a consistent device size.
54 - Add Human readable MiB or GiB value on size lines of Detail and Examine
55 - --assemble --scan doesn't complain about active drives
56 - require number of spares given in -x to be listed.
57 - Made --build actually work.
58Changes Prior to 0.5 release
60 --assemble:
61 spare drives are handled properly.
63 --force can be used to recover from 2-drive failures on RAID5
64 If you belive that /dev/hda1 /dev/hdb1 /dev/hdc1 /dev/hdd1 should
65 make a raid5 array, but it has experienced multiple failures and
66 wont start, then
68 mdctl --assemble --force /dev/md0 /dev/hd[abcd]1
70 Should update the superblock on the newest failed drive and
71 restart the array in degraded mode. You should then remove the
72 remaining failed drive and re-add it (if you are happy that it
73 might work).
75 Ofcourse whenever you have a 2-drive failure, you have a risk
76 of corruption in data that hasn't be changed for a long time. So
77 this doesn't give you your array back all nice and happy, but it
78 does allow you to recover data that might not be corrupt.
80 More flexibility in identifying a RAID array in the mdctl.conf
81 e.g.
82 array /dev/md4 super-minor=4
84 assembles /dev/md4 from all devices found that have a raid
85 superblock that says the minor number of the array is 4.
86 If the blocks with the right minor number do not all have the
87 same UUID, an error is flags and no assembly happens.
89 array /dev/md3 devices=/dev/hd[abc]2
91 Assembles /dev/md3 drom /dev/hda2 /dev/hdb2 and/dev/hdc2. All
92 devices must exist and have raid superblock with the same uuid.
94 If two identity specifiers are used, only devices that match all
95 of them are considered, so
97 array /dev/md2 devices=/dev/hd?2 super-minor=2
99 will assemble /dev/md2 using all /dev/hd?2 devices which have a
100 raid superblock with minor number 2.
102 --create:
103 When listing devices for --create, the word "missing" can be
104 used to indicate that the respective slot does not have a
105 working drive currently. This is similar to the "failed-disk"
106 directive in mkraid/raidtab.
107 e.g.
108 mdctl --create --level=5 -raid-disks=4 --spare-disks=2
109 /dev/md0 /dev/sda /dev/sdb missing /dev/sdc /dev/sdd /dev/sde
111 will create a raid5 array with the third slot empty, and two
112 spares.
114 By default, raid5 arrays are created with the last slot empty
115 and drive listed for the last slot added as a spare. If a
116 "missing" slot is given, or if --force is given, then --create
117 does exactly what you ask and doesn't try to be clever.
120 --follow / --monitor:
122 This is a new mode. I couldn't stop my self from picking a name
123 starting with F (as current modes start A,B,C,D,E) but I
124 relented and provided an alternate name that is somewhat more
125 meaningful.
127 In this mode, mdctl does not exit, but runs continuously and
128 periodically polls all the md devices to see if they have had
129 any interested state change.
130 The changes that it currently notices are:
131 Fail - an active disc fails
132 FailSpare - a spare, that was presumably being build, fails
133 ActiveSpare - a spare becomes active, presumably after a rebuild.
135 Options:
136 --mail mailaddress - send Email on any Fail* event
137 --program program - run the program on any event.
138 Args are: eventname mddevice subdevice(if-known)
139 --delay seconds - change from the default 60second pause
140 between polls.
142 I plan to add functionality to this mode to allow sharing of
143 spare drives. If an array is marks "spare-group=fred", and it
144 has a failed drive and no spares, and if some other array is
145 also "spare-group=fred" and it has no failed drives, but does
146 have a spare drive that is big enough, the spare will be moved
147 to the first array.
149 I also have the idea of adding a --grow mode which will re-organise
150 the data on an N disk raid0/4/5 array to be on an N+M disk array.
151 I have no concrete plans for this though.
153 I got rid of the "v" in the archive file name, and include the
154 version number in the directory created by the archive.
156 There is now a man page and mdctl.spec (for rpm) thanks to
157 Danilo Godec <>.
159 Ofcourse, the man page is now out of date and despite being based on
160 the --help output, is not wholy correct. After I get --follow
161 working properly, I plan to revise the various documentation and/or
162 the code to make sure the two match.