[thirdparty/mdadm.git] / ChangeLog
1Changes Prior to 1.2.0 release
2 - Fix bug where --daemonise required an argument.
3 - In --assemble --verbose, print appropriate message if device is
4 not in devices= list
5 - Updated mdadm.conf.5 to reflect fact that device= takes wildcards
6 - Typos: componenet -> component
7 - Reduce size of "--help" message put excess into "--help-options"
8 - Fix bug introduced when MD_SB_DISKS dependancy removed, and which
9 caused spares not be assembled properly.
10 - Print appropriate message if --monitor --scan decides not to
11 monitor anything.
12Changes Prior to 1.1.0 release
13 - add --deamonise flag for --monitor - forks and prints pid to stdout
14 - Fix bug so we REALLY clear dirty flag with -Af
15 - -Db now prints a 'devices=' word for each array.
16 - "mdadm -A /dev/md0" will get info from configfile, even without scan
17 - When assembling multipath arrays, ignore devices which are flagged
18 as having errors.
19 - take --super-minor=dev to mean "use the minor number of the mddev
20 being assembled.
21 - take --config=none to mean "completely ignore config file"
22 - Make --monitor require --scan or a device list.
23Changes Prior to 1.0.9 release
24 - Documentation updates including kernel parameters documented
25 in md.4
26 - --assemble --force for raid4/5 will mark clean, needed for 2.5
27 - --detail prints out the events counter as well
28 - flush device before reading superblock to be sure to get
29 current data
30 - added mdadm.static target to makefile for static linking
31 - --monitor was ignoring /dev/md0 due to off-by-one error
32 - Fix assorted typos
33 - Fix printing of Gibibytes - calc was wrong.
34 - Fix printing of Array Size in --detail when very big.
35 - --monitor no longer tries to work for raid0 or linear as these
d013a55e 36 have nothing to be monitored.
37 - The word 'partitions' on a DEVICE line will cause all partitions
38 listed in /proc/partitions to be considered
39 - If the config file is called 'partitions' then it will be treated
40 as though it contained exactly 'device partitions' so e.g.
41 mdadm -Ebsc partitions
d013a55e 42 will find all raid partitions easily.
43 - successfully assemble multipath devices by ignoring raid_disk
44 value from superblock (it is always the same).
45 - --assemble not tied to MD_SB_DISKS limit quite so much
46 - Support compiling with tcc
47 - Support compiling with uclibc - just skip scan of /dev
48 - Add --update= option for Assemble mode. Either sparc2.2
49 or super-minor updates are possible. See mdadm.8
51Changes Prior to 1.0.1 release
52 - Round off MB/GiB etc values instead of round down.
53 - Add --sparc2.2 option to examine to shift superblock around
54 and --sparc2.2update to rewrite the superblock
5787fa49 55 - Fix assorted typos in online help
57Changes Prior to 1.0.0 release
58 - Allow --config with Misc mode (for --examine --scan)
59 - Add $(CXFLAGS) to end of CFLAGS in makefile
60 - When making an N disk raid5 array, the Nth drive
61 is moved to the end of the array as a spare rather than
62 being shifted up one place. This means that when the
63 kernel builds onto the last spare and inserts it,
64 the devices will be in the expected order.
65 - Man page improvements
66Changes Prior to 0.8.2 release
67 - Correct spelling of persist[ae]nce/persist[ae]nt.
68 - Change "disk" to "device" in options and config file
69 - convert array size to "long long" *before* shift-left in -D and -Q
71Changes Prior to 0.8.1 release
72 - Add "INSTALL" file.
73 - Fix some "i" variables that were not being set properly
74 - Initialise minsize and maxsize so that compilers don't complain.
75 - Tidy up Makefile and mdadm.spec installations
76 - Add "multipath" to documentation of valid levels
78Changes Prior to 0.8 release
79 - Fix another bug in Assemble.c due to confusing 'i' with 'j'
80 - Minimal, untested, support for multipath
81 - re-write of argument parsing to have more coherent modes,
82 - add --query,-Q option
83 - Update mdadm.8 to reflect arg processing change and --query
84 - Change "long" to "unsigned long" for device sizes
85 - Handle "mailaddr" and "program" lines in config file for follow/scan mode.
86 - --follow --scan will exit if no program or mail found
87 - Add MAILADDR and PROGRAM to mdadm.conf-example
88 - Spell check man pages
89 - consistently use "component devices" instead of "subdevices"
90 - Make -Wall -Werror really work and fix lots of errors.
91 - --detail and --stop can have --scan which chooses devices from /proc/mdstat
92 - --monitor detects 20% changes in resync, failed spares,
93 disappearing arrays,
94 - --monitor --scan will automatically add any devices found in /proc/mdstat
95 - --monitor will move spares between arrays with same spare-group if necessary
96 - Documentation for Monitor Mode
97 - --query notes if the array containing the given device is active or not
98 - Finished md.4 man page.
100Changes Prior to 0.7.2 release
101 - mdadm.spec updates and ifdef BLKGETSIZE64 from Luca Berra --
102 - more mdadm.spec updates from Gregory Leblanc <>
103 - make directory for mdadm.conf configurable in Makefile
104 - Finished mdadm.conf.5. Removed details of conf file from
105 mdadm.8 leaving a reference to mdadm.conf.5.
106 - Fix bug in Assemble.c, thanks to Junaid Rizvi <>
107 - Get --assemble --force to make sure old major/minor numbers are
108 consistant, as md.c worries about this :-(
111Changes Prior to 0.7.1 release
112 - update mdadm.spec
113 - use BLKGETSIZE64 if available for array size
114 - give human readable as GiB/MiB and GB and MB, with 2 decimal point precision
115 - Only warn about size variation for raid1/4/5.
116 - Started md.4 man page
117 - Started mdadm.conf.5 man page
119Changes Prior to 0.7 release
121 - Fix makefile to install binary at /sbin and not /sbin/sbin
122 Also install man page.
123 - Add --zero-superblock based on --destroywithextremeprejudice
124 from Dale Stephenson <>
125 - change name to mdadm. It is palandromic, and much nicer to pronouce.
127Changes Prior to 0.6 release
9a9dab36 129 - Remove the limit on the number of device names that can be
130 given on the command line.
131 - Fix bug in --assemble --force where it would only update a
132 single superblock.
133 - Fix bogus printing of big numbers not being block devices
134 when given names of devices that don't exist.
135 - When --assemble --force, consider superblocks with an event
136 count that is 1 behind as out-of-date. Normally they are
137 considered up-to-date (as the kernel assumes this too).
138 - When marking drives as not-failed in the superblock,
139 we also mark them as ACTIVE and SYNC.
140 - Don't start arrays for which not all drives are available unless:
141 --scan which implies that all drives were found automatically
142 --run which means the user knows what they want
143 --force which means that we are fixing something broken
144 - Make sure all device numbers passed as 3rd arg of ioctl
145 are passed as unsigned lock, so that it works on SPARC
146 - If HOT_ADD_DISK failes for -a, then only try ADD_NEW_DISK
147 if we cannot read from the array, i.e. if the array is
148 not started yet.
149 - man page update
150 - Taught Examine to handle --scan. It examines all devices listed
151 on DEVICE lines in the config file.
152 - Added --brief (-b) flag for Examine and Detail to print out
153 and mdctl.conf compatible description with uuid=, level=,
154 disks= and - for Examine - devices=
155 --examine --brief collects all devices the make the one array and
156 list them as one entry.
157 - Added level= and disks= options to ARRAY lines in config files
158 so --brief output could be used as-is.
159 - Make parity style ({left,right}-{,a}symmetric) consistantly use -,
160 never _.
161 - Add "Array Size" to --detail output
162 - Change "Size" to "Device Size" and exclude from Detail of arrays
163 that do not have a consistent device size.
164 - Add Human readable MiB or GiB value on size lines of Detail and Examine
165 - --assemble --scan doesn't complain about active drives
166 - require number of spares given in -x to be listed.
167 - Made --build actually work.
168Changes Prior to 0.5 release
170 --assemble:
171 spare drives are handled properly.
173 --force can be used to recover from 2-drive failures on RAID5
174 If you belive that /dev/hda1 /dev/hdb1 /dev/hdc1 /dev/hdd1 should
175 make a raid5 array, but it has experienced multiple failures and
176 wont start, then
178 mdctl --assemble --force /dev/md0 /dev/hd[abcd]1
180 Should update the superblock on the newest failed drive and
181 restart the array in degraded mode. You should then remove the
182 remaining failed drive and re-add it (if you are happy that it
183 might work).
185 Ofcourse whenever you have a 2-drive failure, you have a risk
186 of corruption in data that hasn't be changed for a long time. So
187 this doesn't give you your array back all nice and happy, but it
188 does allow you to recover data that might not be corrupt.
190 More flexibility in identifying a RAID array in the mdctl.conf
191 e.g.
192 array /dev/md4 super-minor=4
194 assembles /dev/md4 from all devices found that have a raid
195 superblock that says the minor number of the array is 4.
196 If the blocks with the right minor number do not all have the
197 same UUID, an error is flags and no assembly happens.
199 array /dev/md3 devices=/dev/hd[abc]2
201 Assembles /dev/md3 drom /dev/hda2 /dev/hdb2 and/dev/hdc2. All
202 devices must exist and have raid superblock with the same uuid.
204 If two identity specifiers are used, only devices that match all
205 of them are considered, so
207 array /dev/md2 devices=/dev/hd?2 super-minor=2
209 will assemble /dev/md2 using all /dev/hd?2 devices which have a
210 raid superblock with minor number 2.
212 --create:
213 When listing devices for --create, the word "missing" can be
214 used to indicate that the respective slot does not have a
215 working drive currently. This is similar to the "failed-disk"
216 directive in mkraid/raidtab.
217 e.g.
218 mdctl --create --level=5 -raid-disks=4 --spare-disks=2
219 /dev/md0 /dev/sda /dev/sdb missing /dev/sdc /dev/sdd /dev/sde
221 will create a raid5 array with the third slot empty, and two
222 spares.
224 By default, raid5 arrays are created with the last slot empty
225 and drive listed for the last slot added as a spare. If a
226 "missing" slot is given, or if --force is given, then --create
227 does exactly what you ask and doesn't try to be clever.
230 --follow / --monitor:
232 This is a new mode. I couldn't stop my self from picking a name
233 starting with F (as current modes start A,B,C,D,E) but I
234 relented and provided an alternate name that is somewhat more
235 meaningful.
237 In this mode, mdctl does not exit, but runs continuously and
238 periodically polls all the md devices to see if they have had
239 any interested state change.
240 The changes that it currently notices are:
241 Fail - an active disc fails
242 FailSpare - a spare, that was presumably being build, fails
243 ActiveSpare - a spare becomes active, presumably after a rebuild.
245 Options:
246 --mail mailaddress - send Email on any Fail* event
247 --program program - run the program on any event.
248 Args are: eventname mddevice subdevice(if-known)
249 --delay seconds - change from the default 60second pause
250 between polls.
252 I plan to add functionality to this mode to allow sharing of
253 spare drives. If an array is marks "spare-group=fred", and it
254 has a failed drive and no spares, and if some other array is
255 also "spare-group=fred" and it has no failed drives, but does
256 have a spare drive that is big enough, the spare will be moved
257 to the first array.
259 I also have the idea of adding a --grow mode which will re-organise
260 the data on an N disk raid0/4/5 array to be on an N+M disk array.
261 I have no concrete plans for this though.
263 I got rid of the "v" in the archive file name, and include the
264 version number in the directory created by the archive.
266 There is now a man page and mdctl.spec (for rpm) thanks to
267 Danilo Godec <>.
269 Ofcourse, the man page is now out of date and despite being based on
270 the --help output, is not wholy correct. After I get --follow
271 working properly, I plan to revise the various documentation and/or
272 the code to make sure the two match.