Changes Prior to this release
+ - Try /etc/mdadm/mdadm.conf if /etc/mdadm.conf doesn't exist.
+ This provided compatability for Debian.
+
+Changes Prior to 2.2 release
+ - Assorted bug fixes
+ - Support write-intent-bitmaps on raid10
+ - Support little-endian (Rather than hostendian) bitmaps.
+ - Return correct error code from 'mdadm -S'
+ - Remove extra blank line from 'mdadm -Eb' output.
+ - Improve option parsing so that -a and -b do not have
+ optional arguements: the arg is either required or not
+ depending on context.
+ - Allow scanning of devices listed in /proc/partitions even
+ if they don't appear in /dev.
+ - Support --assume-clean in --create mode as well as --build
+ - Add support for --monitor to report to syslog: -y or --syslog.
+ Thanks to Ross Vandegrift
+ - --monitor now reports which device failed in a 'Fail' message
+ This broke with 2.6
+ - Improve chance of array starting properly after a crash.
+ mdadm was insisting the event numbers were identical, but this
+ isn't needed, and is a problem if the crash was while the metadata
+ was being updated.
+ - Support --update==uuid
+ - Added README.initramfs and mkinitramfs to help people use an
+ initram for starting md arrays at boot.
+
+Changes Prior to 2.1 release
+ - Fix assembling of raid10 array when devices are missing.
+ mdadm now correctly detects if a array is workable or not
+ depending on which devices are present, and so will correctly
+ handle "--assemble --force" if multiple devices have failed.
+ - Report raid10 layout in --examine output.
+ - Fix assembling of arrays that use the version-1 superblock and
+ have spares. Previously the spares would be ignored.
+ - Fix bug so that multiple drives can be re-added at once.
+ - Fix problem with hot-adding a bitmap to version-1-superblock
+ arrays.
+
+Changes Prior to 2.0
- Support assembling from byte-swapped superblocks
metadata type "0.swap" and --update=byteorder
- write-mostly and write-behind support for raid1.
projects / thirdparty / mdadm.git / blobdiff