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