Changes Prior to this release
+ - Don't #include linux/blkpg.h as that isn't safe. Just
+ include the content literally.
+ - Reduce maximum bitmap usage when working with bitmap files,
+ so that a only single-page allocations are made, even on
+ 64bit hosts with 4K pages.
+ - Close stray fd in mdassemble so that it can assemble stacked
+ devices
+ - If mdassemble finds an array already assembled, it marks it
+ read-write.
+ - Remove error in md_open if array is already active. This isn't
+ needed and gets in the ways if an array was created e.g. in
+ initramfs, but device doesn't yet exist in /dev.
+ - When --assemble --scan is run, if all arrays that could be found
+ have already been started, don't report an error.
+ - Fix a couple of bugs related to raid10 and the new 'offset' layout.
+
+Changes Prior to 2.5.4 release
+ - When creating devices in /dev/md/ create matching symlinks
+ from /dev. e.g. /dev/md0 -> /dev/md/0.
+ Allow this to be disabled in mdadm.conf or on command line.
+ - Fix some endian-ness issues with version-1 superblocks (affects
+ bigendian only).
+ - Fix endian problem with 'bitmap' metadata
+ - Allow a number (of partitions) after the 'yes' option to --auto=
+ This is particularly useful in the 'create' line in mdadm.conf.
+ - Remove partitions from any whole device that is made part of
+ an md array. This is a work-around for annoying messages
+ when the first block on some drive accidentally looks like a
+ partition table.
+
+Changes Prior to 2.5.3 release
+ - Document v0.91 superblocks in md.4
+ - Make GPL explicit in man pages.
+ - Fix recent breakage of starting degraded arrays.
+ - Tidyup automatic name choice for v-1 arrays:
+ /dev/md_d0 now becomes '0', not '_d0'.
+
+Changes Prior to 2.5.2 release
+ - Fix problem with compiling with gcc-2 compilers
+ - Fix compile problem of post-incrmenting a variable in a macro arg.
+ - Stop map_dev from returning [0:0], as that breaks things.
+ - Add 'Array Slot' line to --examine for version-1 superblocks
+ to make it a bit easier to see what is happening.
+ - Work around bug in --add handling for version-1 superblocks
+ in 2.6.17 (and prior).
+ - Make -assemble a bit more resilient to finding strange
+ information in superblocks.
+ - Don't claim newly added spares are InSync!! (don't know why that
+ code was ever in there)
+ - Work better when no 'ftw' is available, and check to see
+ if current uclibc provides ftw.
+ - Never use /etc/mdadm.conf if --config file is given (previously
+ some code used one, some used the other).
+
+Changes Prior to 2.5.1 release
+ - Various fixes for gcc warnings
+ - uclibc warnings
+ - Makefile improvements for static linking/intalling
+ - Makefile uninstall target
+ - Really fix return status of --examine
+ - Typos
+ - Byteorder stuff (again)
+ - Don't try to create devices with --manage or --grow
+ - allow default metadata (superblock) type to be specified
+ in mdadm.conf
+ - Get --stop to list devices stopped but honour --quiet
+ - remove libssl dependency
+ - Avoid some misdetection of overlapping partitions
+ - Fix memory leak in --monitor mode
+
+Changes Prior to 2.5 release
- Support 'mailfrom' line in mdadm.conf so the From: line in alert
emails can be explicitly set.
- Arrange that SparesMissing (which is similar in import to
in report.
- When using --update=uuid on an array with a bitmap, update the
bitmap's uuid too.
+ - Add a copy of /proc/mdstat to the mail message sent by mdadm
+ --monitor.
+ - New flag --no-degraded to avoid starting arrays if there are
+ fewer devices available than last time the array was started.
+ This is only needed with --scan, as with --scan, that behaviour
+ is the default.
+ - Support for 'homehost' concept. This is a fairly major update.
+ It includes a configfile option and a command line option for
+ specifying a homehost, records that host in the superblock,
+ and reports the homehost where possible.
+ - Support for Auto Assembly. "mdadm -As" will, if provided with
+ the name of a homehost, try to assemble all arrays it can find
+ that were created for that homehost. See man pages for more details.
Changes Prior to 2.4.1 release
- Honour --write-mostly when adding to an array without persistent
- Change "dirty" status to "active" as it was confusing people.
- --assemble --auto recognises 'standard' name and insists on using
the appropriate major/minor number for them.
- - Remove underscore from partition names, so partitions of
+ - Remove underscore from partition names, so partitions of
"foo" are "foo1", "foo2" etc (unchanged) and partitions of
"f00" are "f00p1", "f00p2" etc rather than "f00_p1"...
- - Use "major", "minor", "makedev" macros instead of
+ - Use "major", "minor", "makedev" macros instead of
"MAJOR", "MINOR", "MKDEV" so that large device numbers work
on 2.6 (providing you have glibc 2.3.3 or later).
- Add some missing closes of open file descriptors.
- Restore support for uclibc which was broken recently.
- Several improvements to the output of --detail, including
reporting "resyncing" or "recovering" in the state.
- - Close filedescriptor at end of --detail (exit would have closed it
+ - Close filedescriptor at end of --detail (exit would have closed it
anyway, so this isn't abig deal).
- Report "Sync checkpoint" in --examine output if appropriate.
- Add --update=resync for --assemble mode to for a resync when the
- array is assembled.
+ array is assembled.
- Add support for "raid10", which is under development in 2.6.
Not documented yet.
- --monitor now reads spare-group and spares info from config file
- Support "--monitor --test" which will generate a test alert
for each array once, to test notification paths.
- Generate RebuildFinished event when rebuild finishes.
- - Support for raid6 as found in 2.6.2 - thanks to
+ - Support for raid6 as found in 2.6.2 - thanks to
H. Peter Anvin <hpa@zytor.com>
- Support partitioned md arrays with a different major number and
naming scheme (md_dX in /proc/mdstat, /dev/md/dXpY in /dev).
- Fix bug introduced when MD_SB_DISKS dependancy removed, and which
caused spares not be assembled properly.
- Print appropriate message if --monitor --scan decides not to
- monitor anything.
+ monitor anything.
Changes Prior to 1.1.0 release
- add --deamonise flag for --monitor - forks and prints pid to stdout
- Fix bug so we REALLY clear dirty flag with -Af
- "mdadm -A /dev/md0" will get info from configfile, even without scan
- When assembling multipath arrays, ignore devices which are flagged
as having errors.
- - take --super-minor=dev to mean "use the minor number of the mddev
+ - take --super-minor=dev to mean "use the minor number of the mddev
being assembled.
- take --config=none to mean "completely ignore config file"
- Make --monitor require --scan or a device list.
- Remove the limit on the number of device names that can be
given on the command line.
- - Fix bug in --assemble --force where it would only update a
+ - Fix bug in --assemble --force where it would only update a
single superblock.
- Fix bogus printing of big numbers not being block devices
when given names of devices that don't exist.
- When --assemble --force, consider superblocks with an event
count that is 1 behind as out-of-date. Normally they are
considered up-to-date (as the kernel assumes this too).
- - When marking drives as not-failed in the superblock,
+ - When marking drives as not-failed in the superblock,
we also mark them as ACTIVE and SYNC.
- Don't start arrays for which not all drives are available unless:
--scan which implies that all drives were found automatically
not started yet.
- man page update
- Taught Examine to handle --scan. It examines all devices listed
- on DEVICE lines in the config file.
+ on DEVICE lines in the config file.
- Added --brief (-b) flag for Examine and Detail to print out
and mdctl.conf compatible description with uuid=, level=,
disks= and - for Examine - devices=
- --examine --brief collects all devices the make the one array and
+ --examine --brief collects all devices the make the one array and
list them as one entry.
- Added level= and disks= options to ARRAY lines in config files
so --brief output could be used as-is.
superblock that says the minor number of the array is 4.
If the blocks with the right minor number do not all have the
same UUID, an error is flags and no assembly happens.
-
+
array /dev/md3 devices=/dev/hd[abc]2
Assembles /dev/md3 drom /dev/hda2 /dev/hdb2 and/dev/hdc2. All
array /dev/md2 devices=/dev/hd?2 super-minor=2
- will assemble /dev/md2 using all /dev/hd?2 devices which have a
+ will assemble /dev/md2 using all /dev/hd?2 devices which have a
raid superblock with minor number 2.
-
+
--create:
When listing devices for --create, the word "missing" can be
used to indicate that the respective slot does not have a
and drive listed for the last slot added as a spare. If a
"missing" slot is given, or if --force is given, then --create
does exactly what you ask and doesn't try to be clever.
-
+
--follow / --monitor:
This is a new mode. I couldn't stop my self from picking a name
starting with F (as current modes start A,B,C,D,E) but I
relented and provided an alternate name that is somewhat more
- meaningful.
-
+ meaningful.
+
In this mode, mdctl does not exit, but runs continuously and
periodically polls all the md devices to see if they have had
any interested state change.
Options:
--mail mailaddress - send Email on any Fail* event
- --program program - run the program on any event.
+ --program program - run the program on any event.
Args are: eventname mddevice subdevice(if-known)
--delay seconds - change from the default 60second pause
between polls.
There is now a man page and mdctl.spec (for rpm) thanks to
Danilo Godec <danci@agenda.si>.
-
+
Ofcourse, the man page is now out of date and despite being based on
the --help output, is not wholy correct. After I get --follow
working properly, I plan to revise the various documentation and/or
projects / thirdparty / mdadm.git / blobdiff