-Changes Prior to this release
+Changed Prior to this release
+ - --readwrite can be used with --re-add to clear the writemostly
+ flag.
+
+Changes Prior to 2.6.7 release
+ - Avoid NULL reference calling free_super and elsewhere.
+ - Remove stray semicolon (Causes compile error with gcc-2.95)
+ - Fix autoassemble for stack arrays.
+
+Changes Prior to 2.6.6 release
+ - "make everything" now make mdassemble.auto
+ - fix compile problem with mdassemble.auto
+ - Update FAQ URLs in man page again.
+
+Changes Prior to 2.6.5 release
+ - Avoid segfault when parsing /proc/mdstat with auto-read-only
+ arrays.
+ - Fix problem with failing to add devices to v.large (>4TB) arrays,
+ cause by problems with device-size overflow.
+ - For v0.90 superblocks, print the 'Events' count as a real count,
+ not 2 numbers separated by a dot.
+ - Updates some URLs in the man page.
+ - Allow creation of a RAID6 with exactly one missing device.
+ - Use LOG_PID for syslog, so you get the pid of mdadm in the log
+ files.
+ - --export now works with --examine too (not just --detail)
+ - Improve auto-creation of device special file when using
+ --incremental
+ - Simple locking for --incremental so mdadm doesn't get confused
+ when run concurrently with itself.
+ - Make --incremental cope better with arrays that are being reshaped.
+
+Changes Prior to 2.6.4 release
+ - Make "--create --auto=mdp" work for non-standard device names.
+ - Fix restarting of a 'reshape' if it was stopped in the middle.
+ - Fix a segfault when using v1 superblock.
+ - Make --write-mostly effective when re-adding a device to an array.
+ - Various minor fixes
+
+Changes Prior to 2.6.3 release
+ - allow --write-behind to be set for --grow.
+ - When adding new disk to an array, don't reserve so much bitmap
+ space that the disk cannot store the required data. (Needed when
+ 1.x array was created with older mdadm).
+ - When adding a drive that was a little too small, we did not get
+ the correct error message.
+ - Make sure that if --assemble find an array in the critical region
+ of a reshape, and cannot find the critical data to restart the
+ reshape, it gives an error message.
+ - Fix segfault with '--detail --export' and non-persistent
+ superblocks.
+ - Various manpage updates.
+ - Improved 'raid4' support (--assemble, --monitor)
+ - Option parsing fixes w.r.t -a
+ - Interpret "--assemble --metadata=1" to allow any version 1.x
+ metadata, and be more specific in the "metadata=" message printed
+ with --examine --brief
+ - Fix spare migration in --monitor.
+
+Changes Prior to 2.6.2 release
+ - --fail detached and --remove faulty can be used to fail and
+ remove devices that are no longer physically present.
+ - --export option for --detail or present information in a format
+ that can be processed by udev.
+ - fix internal bitmap allocation problems with v1.1, v1.2 metadata.
+ - --help now goes to stdout so you can direct it to a pager.
+ - Various manpage updates.
+ - Make "--grow --add" for linear arrays really work.
+ - --auto-detect to trigger in-kernel autodetect.
+ - Make return code for "--detail --test" more reliable. Missing
+ devices as well as failed devices cause an error.
+
+Changes Prior to 2.6.1 release
+ - --monitor was producing some meaningless warnings due to a bug.
+ - Fix some compiler warnings.
+ - Fully support --grow for raid6. If a reshape crashed during the
+ critical period, mdadm wouldn't restore the Q information
+ properly.
+ - Update documentation for --grow.
+
+Changes Prior to 2.6 release
+ - Fixed UUID printing in "--detail --brief" for version1 metadata.
+ - --update=resync did exactly the wrong thing for version1 metadata.
+ It caused a resync to not happen, rather than to happen.
+ - Allow --assemble --force to mark a raid6 clean when it has two
+ missing devices (which is needed else if won't assemble.
+ Without this fix it would only assemble if one or zero
+ missing devices.
+ - Support --update=devicesize for cases where the underlying device
+ can change size.
+ - Default to --auto=yes so the array devices with 'standard' names
+ get created automatically, as this is almost always what is wanted.
+ - Give useful message if raid4/5/6 cannot be started because it is
+ not clean and is also degraded.
+ - Increase raid456 stripe cache size if needed to --grow the array.
+ The setting used unfortunately requires intimate knowledge of the
+ kernel, and it not reset when the reshape finishes.
+ - Change 'Device Size' to 'Used Dev Size' because it only shows how
+ much of each device is actually used, not how big they are.
+ - --wait or -W will wait for resync activity to finish on the given
+ devices.
+ - Fix some problems with --update=uuid and add a test.
+ - If two drives in a raid5 disappear at the same time, then "-Af"
+ will add them both in rather than just one and forcing the array
+ to 'clean'. This is slightly safer in some cases.
+ - Check device is large enough before hot-add: this improves quality
+ of error message.
+ - Don't hold md device open for so long in --monitor mode - map_dev
+ can be slow and interferes with trying to stop the array.
+ - Support --uuid= with --create to choose your own UUID.
+ - New major more "--incremental" for incremental assemble of arrays,
+ intended for use with udev.
+
+Changes Prior to 2.5.6 release
+ - Fix bug which meant "bitmap=xxx" in mdadm.conf was not handled
+ properly.
+ - Documentation updates.
+ - Fix bug that caused infinite loop when doing auto-assembly,
+ in certain cases where arrays couldn't be assembled.
+
+Changes Prior to 2.5.5 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,
- 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.
+ - Improve error message when a wrong '--update' option is given.
Changes Prior to 2.5.4 release
- When creating devices in /dev/md/ create matching symlinks