projects / thirdparty / mdadm.git / blame
| Commit | Line | Data |
|---|---|---|
| 850a3178 N |
1 | Subject: ANNOUNCE: mdadm 3.1.3 - A tool for managing Soft RAID under Linux |
| 2 | ||
| 3 | I am pleased to announce the availability of | |
| 4 | mdadm version 3.1.3 | |
| 5 | ||
| 6 | It is available at the usual places: | |
| 7 | countrycode=xx. | |
| 8 | http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/ | |
| 9 | and via git at | |
| 10 | git://neil.brown.name/mdadm | |
| 11 | http://neil.brown.name/git?p=mdadm | |
| 12 | ||
| 13 | This is a bugfix/stability release over 3.1.2 | |
| 14 | ||
| 15 | Significant changes are: | |
| 16 | - mapfile now lives in a fixed location which default to | |
| 17 | /dev/.mdadm/map but can be changed at compile time. This | |
| 18 | location is choses and most distros provide it during early | |
| 19 | boot and preserve it through. As long a /dev exists and is | |
| 20 | writable, /dev/.mdadm will be created. | |
| 21 | Other files file communication with mdmon live here too. | |
| 22 | This fixes a bug reported by Debian and Gentoo users where | |
| 23 | udev would spin in early-boot. | |
| 24 | - IMSM and DDF metadata will not be recognised on partitions | |
| 25 | as they should only be used on whole-disks. | |
| 26 | - Various overflows causes by 2G drives have been addressed. | |
| 27 | - A subarray of an IMSM contain can now be killed with | |
| 28 | --kill-subarray. Also subarrays can be renamed with | |
| 29 | --update-subarray | |
| 30 | - -If (or --incremental --fail) can be used from udev to | |
| 31 | fail and remove from all arrays a device which has been | |
| 32 | unplugged from the system. i.e. hot-unplug-support. | |
| 33 | - "mdadm /dev/mdX --re-add missing" will look for any device | |
| 34 | that looks like it should be a member of /dev/mdX but isn't | |
| 35 | and will automatically --re-add it | |
| 36 | - Now compile with -Wextra to get extra warnings. | |
| 37 | - Lots of minor bug fixes, documentation improvements, etcc | |
| 38 | ||
| 39 | This release is believed to be stable and you should feel free to | |
| 40 | upgrade to 3.1.3 | |
| 41 | ||
| 42 | It is expected that the next release will be 3.2 with a number of new | |
| 43 | features. 3.1.4 will only happen if important bugs show up before 3.2 | |
| 44 | is stable. | |
| 45 | ||
| 46 | NeilBrown 6th August 2010 |