]> git.ipfire.org Git - thirdparty/mdadm.git/blob - ChangeLog
Add some missing closes of mdfd
[thirdparty/mdadm.git] / ChangeLog
1 Changes Prior to 1.9.0 release
2 - Fix rpm build problem (stray %)
3 - Minor manpage updates
4 - Change "dirty" status to "active" as it was confusing people.
5 - --assemble --auto recognises 'standard' name and insists on using
6 the appropriate major/minor number for them.
7 - Remove underscore from partition names, so partitions of
8 "foo" are "foo1", "foo2" etc (unchanged) and partitions of
9 "f00" are "f00p1", "f00p2" etc rather than "f00_p1"...
10 - Use "major", "minor", "makedev" macros instead of
11 "MAJOR", "MINOR", "MKDEV" so that large device numbers work
12 on 2.6 (providing you have glibc 2.3.3 or later).
13 - Add some missing closes of open file descriptors.
14
15 Changes Prior to 1.8.0 release
16 - Makefile cleanup from Luca Berra <bluca@comedia.it>
17 - --pid-file (-i) to set a pid file to use with --monitor --daemonise
18 - Fix typo in mdadm man page
19 - Fix coredump when "-s" used with no config file present.
20 - Support new "faulty" personality which can inject synthetic
21 faults. (Not in kernel.org yet at 1Nov2004)
22 - Support raid0/linear on devices > 2 Terabytes
23 - Make sure raid6 resyncs when created with one missing device
24
25 Changes Prior to 1.7.0 release
26 - Support "--grow --add" to add a device to a linear array, if the
27 kernel supports it. Not documented yet.
28 - Restore support for uclibc which was broken recently.
29 - Several improvements to the output of --detail, including
30 reporting "resyncing" or "recovering" in the state.
31 - Close filedescriptor at end of --detail (exit would have closed it
32 anyway, so this isn't abig deal).
33 - Report "Sync checkpoint" in --examine output if appropriate.
34 - Add --update=resync for --assemble mode to for a resync when the
35 array is assembled.
36 - Add support for "raid10", which is under development in 2.6.
37 Not documented yet.
38 - --monitor now reads spare-group and spares info from config file
39 even when names of arrays to scan are given on the command line
40
41 Changes Prior to 1.6.0 release
42 - Device name given in -Eb is determined by examining /dev rather
43 than assuming /dev/md%d
44 - Fix bug in --monitor where an array could be held open an so
45 could not be stopped without killing mdadm.
46 - Add --grow mode. Currently only --size and --raid-disks can be
47 changed. Both require kernel support which, at the time of
48 writing, is not in a release kernel yet.
49 - Don't print out "errors" or "no-errors" in -D and -E, as the bit
50 is never set or used.
51 - Use md event notification in 2.6.??? to make --monitor mode
52 respond instantly to events.
53 - Add --auto= option and auto= configfile entry to tell mdadm to
54 create device files as needed. This is particularly useful
55 with partitioned arrays where the major device number can change.
56 - When generating --brief listing, if the standard name doesn't
57 exist, search /dev for one rather than using a temp name.
58 - Allow --build to build raid1 and multipath arrays.
59 - Add "--assume-clean" for Create and Build, particularly for raid1
60 Note: this is dangerous. Only use it if you are certain.
61 - Fix bug so that Rebuild status monitoring works again.
62 - Add "degraded" and "recovering" options to the "Status:"
63 entry for --detail
64
65 Changes Prior to 1.5.0 release
66 - new commands "mdassemble" which is a stripped-down equivalent of
67 "mdadm -As", that can be compiled with dietlibc.
68 Thanks to Luca Berra <bluca@comedia.it>.
69 It can be using in an initramfs or initrd.
70 - Fix compiling error with BLKGETSIZE64 and some signed/unsigned
71 comparison warnings.
72 - Add Rebuild Status (% complete) to --detail output.
73 - Support "--monitor --test" which will generate a test alert
74 for each array once, to test notification paths.
75 - Generate RebuildFinished event when rebuild finishes.
76 - Support for raid6 as found in 2.6.2 - thanks to
77 H. Peter Anvin <hpa@zytor.com>
78 - Support partitioned md arrays with a different major number and
79 naming scheme (md_dX in /proc/mdstat, /dev/md/dXpY in /dev).
80
81 Changes Prior to 1.4.0 release
82 - Document fact that creating a raid5 array really creates a
83 degraded array with a spare.
84 - Add "spares=" tag to config file and generate it wit --detail and
85 --examine
86 - Add "SparesMissing" event when --monitor first sees an array and
87 it doesn't have the enough spare devices.
88 - Add --update=summaries for --assemble to update summary
89 information in superblock, and correct other inconsistancies in
90 the superblock.
91 - Add --test option to --detail to set a meaningful exit status.
92
93 Changes Prior to 1.3.0 release
94 - Make 'size' and unsigned long in Create to allow creation of
95 larger arrays.
96 - Explicitly flag spare devices as 'spare' in --detail and --examine
97 output. Previously they simply had no flags lists.
98 - Make MailCmd (for monitor) configurable in Makefile, and default
99 to "/usr/sbin/sendmail -t". Also split out the warning related
100 flags into CWFLAGS for easier build configurability.
101 - Minor bugfix in Manage code.
102 - --monitor now notices and reports degraded arrays at startup using
103 "DegradedArray" event, and also has a --oneshot option to only
104 report DegradedArrays, and then exit.
105 - Small man-page clarification w.r.t. raid levels and raid4 in
106 particular.
107 - Disallow creation of arrays with only one device as this is
108 probably a mistake. --force will override this check.
109 - Correct some misleading documentation in the "mdadm --create --help"
110 message.
111 - Ignore chunksize if raid1 or multipath.
112 - Explicit statement in man page that raid-disks cannot be changed
113 after array is created.
114 - Improve message when attempting to start an array with
115 insufficient devices. Instead of required the array to be full,
116 we only require it has as many active devices as last time.
117
118 Changes Prior to 1.2.0 release
119 - Fix bug where --daemonise required an argument.
120 - In --assemble --verbose, print appropriate message if device is
121 not in devices= list
122 - Updated mdadm.conf.5 to reflect fact that device= takes wildcards
123 - Typos: componenet -> component
124 - Reduce size of "--help" message put excess into "--help-options"
125 - Fix bug introduced when MD_SB_DISKS dependancy removed, and which
126 caused spares not be assembled properly.
127 - Print appropriate message if --monitor --scan decides not to
128 monitor anything.
129 Changes Prior to 1.1.0 release
130 - add --deamonise flag for --monitor - forks and prints pid to stdout
131 - Fix bug so we REALLY clear dirty flag with -Af
132 - -Db now prints a 'devices=' word for each array.
133 - "mdadm -A /dev/md0" will get info from configfile, even without scan
134 - When assembling multipath arrays, ignore devices which are flagged
135 as having errors.
136 - take --super-minor=dev to mean "use the minor number of the mddev
137 being assembled.
138 - take --config=none to mean "completely ignore config file"
139 - Make --monitor require --scan or a device list.
140 Changes Prior to 1.0.9 release
141 - Documentation updates including kernel parameters documented
142 in md.4
143 - --assemble --force for raid4/5 will mark clean, needed for 2.5
144 - --detail prints out the events counter as well
145 - flush device before reading superblock to be sure to get
146 current data
147 - added mdadm.static target to makefile for static linking
148 - --monitor was ignoring /dev/md0 due to off-by-one error
149 - Fix assorted typos
150 - Fix printing of Gibibytes - calc was wrong.
151 - Fix printing of Array Size in --detail when very big.
152 - --monitor no longer tries to work for raid0 or linear as these
153 have nothing to be monitored.
154 - The word 'partitions' on a DEVICE line will cause all partitions
155 listed in /proc/partitions to be considered
156 - If the config file is called 'partitions' then it will be treated
157 as though it contained exactly 'device partitions' so e.g.
158 mdadm -Ebsc partitions
159 will find all raid partitions easily.
160 - successfully assemble multipath devices by ignoring raid_disk
161 value from superblock (it is always the same).
162 - --assemble not tied to MD_SB_DISKS limit quite so much
163 - Support compiling with tcc
164 - Support compiling with uclibc - just skip scan of /dev
165 - Add --update= option for Assemble mode. Either sparc2.2
166 or super-minor updates are possible. See mdadm.8
167
168 Changes Prior to 1.0.1 release
169 - Round off MB/GiB etc values instead of round down.
170 - Add --sparc2.2 option to examine to shift superblock around
171 and --sparc2.2update to rewrite the superblock
172 - Fix assorted typos in online help
173
174 Changes Prior to 1.0.0 release
175 - Allow --config with Misc mode (for --examine --scan)
176 - Add $(CXFLAGS) to end of CFLAGS in makefile
177 - When making an N disk raid5 array, the Nth drive
178 is moved to the end of the array as a spare rather than
179 being shifted up one place. This means that when the
180 kernel builds onto the last spare and inserts it,
181 the devices will be in the expected order.
182 - Man page improvements
183 Changes Prior to 0.8.2 release
184 - Correct spelling of persist[ae]nce/persist[ae]nt.
185 - Change "disk" to "device" in options and config file
186 - convert array size to "long long" *before* shift-left in -D and -Q
187
188 Changes Prior to 0.8.1 release
189 - Add "INSTALL" file.
190 - Fix some "i" variables that were not being set properly
191 - Initialise minsize and maxsize so that compilers don't complain.
192 - Tidy up Makefile and mdadm.spec installations
193 - Add "multipath" to documentation of valid levels
194
195 Changes Prior to 0.8 release
196 - Fix another bug in Assemble.c due to confusing 'i' with 'j'
197 - Minimal, untested, support for multipath
198 - re-write of argument parsing to have more coherent modes,
199 - add --query,-Q option
200 - Update mdadm.8 to reflect arg processing change and --query
201 - Change "long" to "unsigned long" for device sizes
202 - Handle "mailaddr" and "program" lines in config file for follow/scan mode.
203 - --follow --scan will exit if no program or mail found
204 - Add MAILADDR and PROGRAM to mdadm.conf-example
205 - Spell check man pages
206 - consistently use "component devices" instead of "subdevices"
207 - Make -Wall -Werror really work and fix lots of errors.
208 - --detail and --stop can have --scan which chooses devices from /proc/mdstat
209 - --monitor detects 20% changes in resync, failed spares,
210 disappearing arrays,
211 - --monitor --scan will automatically add any devices found in /proc/mdstat
212 - --monitor will move spares between arrays with same spare-group if necessary
213 - Documentation for Monitor Mode
214 - --query notes if the array containing the given device is active or not
215 - Finished md.4 man page.
216
217 Changes Prior to 0.7.2 release
218 - mdadm.spec updates and ifdef BLKGETSIZE64 from Luca Berra -- bluca@comedia.it
219 - more mdadm.spec updates from Gregory Leblanc <gleblanc@linuxweasel.com>
220 - make directory for mdadm.conf configurable in Makefile
221 - Finished mdadm.conf.5. Removed details of conf file from
222 mdadm.8 leaving a reference to mdadm.conf.5.
223 - Fix bug in Assemble.c, thanks to Junaid Rizvi <domdev@sat.net.pk>
224 - Get --assemble --force to make sure old major/minor numbers are
225 consistant, as md.c worries about this :-(
226
227
228 Changes Prior to 0.7.1 release
229 - update mdadm.spec
230 - use BLKGETSIZE64 if available for array size
231 - give human readable as GiB/MiB and GB and MB, with 2 decimal point precision
232 - Only warn about size variation for raid1/4/5.
233 - Started md.4 man page
234 - Started mdadm.conf.5 man page
235
236 Changes Prior to 0.7 release
237
238 - Fix makefile to install binary at /sbin and not /sbin/sbin
239 Also install man page.
240 - Add --zero-superblock based on --destroywithextremeprejudice
241 from Dale Stephenson <steph@snapserver.com>
242 - change name to mdadm. It is palandromic, and much nicer to pronouce.
243
244 Changes Prior to 0.6 release
245
246 - Remove the limit on the number of device names that can be
247 given on the command line.
248 - Fix bug in --assemble --force where it would only update a
249 single superblock.
250 - Fix bogus printing of big numbers not being block devices
251 when given names of devices that don't exist.
252 - When --assemble --force, consider superblocks with an event
253 count that is 1 behind as out-of-date. Normally they are
254 considered up-to-date (as the kernel assumes this too).
255 - When marking drives as not-failed in the superblock,
256 we also mark them as ACTIVE and SYNC.
257 - Don't start arrays for which not all drives are available unless:
258 --scan which implies that all drives were found automatically
259 --run which means the user knows what they want
260 --force which means that we are fixing something broken
261 - Make sure all device numbers passed as 3rd arg of ioctl
262 are passed as unsigned lock, so that it works on SPARC
263 - If HOT_ADD_DISK failes for -a, then only try ADD_NEW_DISK
264 if we cannot read from the array, i.e. if the array is
265 not started yet.
266 - man page update
267 - Taught Examine to handle --scan. It examines all devices listed
268 on DEVICE lines in the config file.
269 - Added --brief (-b) flag for Examine and Detail to print out
270 and mdctl.conf compatible description with uuid=, level=,
271 disks= and - for Examine - devices=
272 --examine --brief collects all devices the make the one array and
273 list them as one entry.
274 - Added level= and disks= options to ARRAY lines in config files
275 so --brief output could be used as-is.
276 - Make parity style ({left,right}-{,a}symmetric) consistantly use -,
277 never _.
278 - Add "Array Size" to --detail output
279 - Change "Size" to "Device Size" and exclude from Detail of arrays
280 that do not have a consistent device size.
281 - Add Human readable MiB or GiB value on size lines of Detail and Examine
282 - --assemble --scan doesn't complain about active drives
283 - require number of spares given in -x to be listed.
284 - Made --build actually work.
285 Changes Prior to 0.5 release
286
287 --assemble:
288 spare drives are handled properly.
289
290 --force can be used to recover from 2-drive failures on RAID5
291 If you belive that /dev/hda1 /dev/hdb1 /dev/hdc1 /dev/hdd1 should
292 make a raid5 array, but it has experienced multiple failures and
293 wont start, then
294
295 mdctl --assemble --force /dev/md0 /dev/hd[abcd]1
296
297 Should update the superblock on the newest failed drive and
298 restart the array in degraded mode. You should then remove the
299 remaining failed drive and re-add it (if you are happy that it
300 might work).
301
302 Ofcourse whenever you have a 2-drive failure, you have a risk
303 of corruption in data that hasn't be changed for a long time. So
304 this doesn't give you your array back all nice and happy, but it
305 does allow you to recover data that might not be corrupt.
306
307 More flexibility in identifying a RAID array in the mdctl.conf
308 e.g.
309 array /dev/md4 super-minor=4
310
311 assembles /dev/md4 from all devices found that have a raid
312 superblock that says the minor number of the array is 4.
313 If the blocks with the right minor number do not all have the
314 same UUID, an error is flags and no assembly happens.
315
316 array /dev/md3 devices=/dev/hd[abc]2
317
318 Assembles /dev/md3 drom /dev/hda2 /dev/hdb2 and/dev/hdc2. All
319 devices must exist and have raid superblock with the same uuid.
320
321 If two identity specifiers are used, only devices that match all
322 of them are considered, so
323
324 array /dev/md2 devices=/dev/hd?2 super-minor=2
325
326 will assemble /dev/md2 using all /dev/hd?2 devices which have a
327 raid superblock with minor number 2.
328
329 --create:
330 When listing devices for --create, the word "missing" can be
331 used to indicate that the respective slot does not have a
332 working drive currently. This is similar to the "failed-disk"
333 directive in mkraid/raidtab.
334 e.g.
335 mdctl --create --level=5 -raid-disks=4 --spare-disks=2
336 /dev/md0 /dev/sda /dev/sdb missing /dev/sdc /dev/sdd /dev/sde
337
338 will create a raid5 array with the third slot empty, and two
339 spares.
340
341 By default, raid5 arrays are created with the last slot empty
342 and drive listed for the last slot added as a spare. If a
343 "missing" slot is given, or if --force is given, then --create
344 does exactly what you ask and doesn't try to be clever.
345
346
347 --follow / --monitor:
348
349 This is a new mode. I couldn't stop my self from picking a name
350 starting with F (as current modes start A,B,C,D,E) but I
351 relented and provided an alternate name that is somewhat more
352 meaningful.
353
354 In this mode, mdctl does not exit, but runs continuously and
355 periodically polls all the md devices to see if they have had
356 any interested state change.
357 The changes that it currently notices are:
358 Fail - an active disc fails
359 FailSpare - a spare, that was presumably being build, fails
360 ActiveSpare - a spare becomes active, presumably after a rebuild.
361
362 Options:
363 --mail mailaddress - send Email on any Fail* event
364 --program program - run the program on any event.
365 Args are: eventname mddevice subdevice(if-known)
366 --delay seconds - change from the default 60second pause
367 between polls.
368
369 I plan to add functionality to this mode to allow sharing of
370 spare drives. If an array is marks "spare-group=fred", and it
371 has a failed drive and no spares, and if some other array is
372 also "spare-group=fred" and it has no failed drives, but does
373 have a spare drive that is big enough, the spare will be moved
374 to the first array.
375
376 I also have the idea of adding a --grow mode which will re-organise
377 the data on an N disk raid0/4/5 array to be on an N+M disk array.
378 I have no concrete plans for this though.
379
380 I got rid of the "v" in the archive file name, and include the
381 version number in the directory created by the archive.
382
383 There is now a man page and mdctl.spec (for rpm) thanks to
384 Danilo Godec <danci@agenda.si>.
385
386 Ofcourse, the man page is now out of date and despite being based on
387 the --help output, is not wholy correct. After I get --follow
388 working properly, I plan to revise the various documentation and/or
389 the code to make sure the two match.