Fix bugs related to raid10 and the new offset layout.

[thirdparty/mdadm.git] / ChangeLog

diff --git a/ChangeLog b/ChangeLog
index ac11d1ad34c500bec439e788f9bcc009cfcb4563..1aaa1ee6d8ff9d8567c1b185b75309da666d430c 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,9 +1,33 @@
 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