Fedora 17 Update: mdadm-3.2.5-3.fc17
updates at fedoraproject.org
updates at fedoraproject.org
Wed Jul 11 23:55:14 UTC 2012
--------------------------------------------------------------------------------
Fedora Update Notification
FEDORA-2012-9946
2012-06-26 20:47:51
--------------------------------------------------------------------------------
Name : mdadm
Product : Fedora 17
Version : 3.2.5
Release : 3.fc17
URL : http://www.kernel.org/pub/linux/utils/raid/mdadm/
Summary : The mdadm program controls Linux md devices (software RAID arrays)
Description :
The mdadm program is used to create, manage, and monitor Linux MD (software
RAID) devices. As such, it provides similar functionality to the raidtools
package. However, mdadm is a single program, and it can perform
almost all functions without a configuration file, though a configuration
file can be used to help with some common tasks.
--------------------------------------------------------------------------------
Update Information:
This is an update to the mdadm package, based on the latest upstream release, mdadm-3.2.5, which fixes a large number of bugs.
Fixes and enhancements include:
- Fix problem where reshape of RAID volume is broken after trying to stop all MD devices.
- Enhance raid-check to allow the adming to specify the max number of concurrent arrays to be checked at any given time.
- Fix uninstall script to remove dangling symlink to mdmonitor-takeover.service, if the mdadm package is uninstalled from the system.
- Fix bug in the upstream mdadm-3.2.4 release where --add would fail in common situations.
- Fix Monitor mode sometimes crashes when a resync completes
- Fix missing symlink for mdadm container device when incremental creates the array
- Make sure when creating a second array in a container that the second array uses all available space since leaving space for a third array is invalid
- Validate the number of imsm volumes per controller
- Fix issues with imsm arrays and disks larger than 2TB
- Add support for expanding imsm arrays/containers
- The support for expanding imsm arrays/containers was accepted upstream, update to the official patches from there
- Fix for the issue of --add not being very smart
- Fix an issue causing rebuilds to fail to restart on reboot (data corrupter level problem)
- Reset the bad flag on map file updates
- Correctly fix failure when trying to add internal bitmap to 1.0 arrays
- Fix bug where IMSM arrays stay inactive in case a reboot is performed during the reshape process.
- Fix issue when re-adding drive to a raid1 array with bitmap
- Fix bug in the handling of raid arrays using a bitmap, preventing the automatic re-add to the array of a temporarily disconnected drive.
All users of mdadm RAIDs are encouraged to upgrade.
--------------------------------------------------------------------------------
ChangeLog:
* Mon Jun 25 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.5-3
- Fix problem where reshape of RAID volume is broken after trying to
stop all MD devices.
- Enhance raid-check to allow the adming to specify the max number of
concurrent arrays to be checked at any given time.
- Resolves bz830177, bz820124
* Wed Jun 13 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.5-2
- Fix uninstall script to remove dangling symlink to
mdmonitor-takeover.service, if the mdadm package is uninstalled from
the system.
- Resolves bz828354
* Mon May 21 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.5-1
- Upgrade to mdadm-3.2.5
- Resolves bz822850
* Tue May 15 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.4-3
- Fix mdadm-3.2.4 introduced bug where --add fails in common cases
- Resolves bz821717 (f17) bz821718 (f16) bz821719 (f15)
* Thu May 10 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.4-2
- Fix mdadm.conf to use 'd' for /var/run/mdadm creation, to avoid the
map file getting deleted during boot.
* Thu May 10 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.4-1
- Upgrade to mdadm-3.2.4
- Resolves bz820534 (rawhide) bz820527 (f17) bz820531 (f16) bz820532 (f15)
* Mon Apr 30 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.3-9
- Fix Monitor mode sometimes crashes when a resync completes
- Fix missing symlink for mdadm container device when incremental creates
the array
- Make sure when creating a second array in a container that the second
array uses all available space since leaving space for a third array
is invalid
- Validate the number of imsm volumes per controller
- Fix issues with imsm arrays and disks larger than 2TB
- Add support for expanding imsm arrays/containers
- The support for expanding imsm arrays/containers was accepted upstream,
update to the official patches from there
- Fix for the issue of --add not being very smart
- Fix an issue causing rebuilds to fail to restart on reboot (data
corrupter level problem)
- Reset the bad flag on map file updates
- Correctly fix failure when trying to add internal bitmap to 1.0 arrays
- Resolves: bz817023 (f17) bz817024 (f17) bz817026 (f17) bz817028 (f17)
- Resolves: bz817029 (f17) bz817032 (f17) bz817038 (f17) bz808774 (f17)
- Resolves: bz817039 (f17) bz817042 (f17)
* Mon Apr 30 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.3-8
- Fix bug where IMSM arrays stay inactive in case a reboot is
- performed during the reshape process.
- Resolves: bz817522 (f17) bz817535 (f16) bz817537 (f15)
* Wed Mar 28 2012 Jes Sorensen <Jes.Sorensen at redhat.com> - 3.2.3-7
- Fix issue when re-adding drive to a raid1 array with bitmap
- Resolves: bz807743 (f17) bz769323 (f16) bz791159 (f15)
--------------------------------------------------------------------------------
References:
[ 1 ] Bug #830177 - Reshape of RAID volume is broken after trying to stop all MD devices
https://bugzilla.redhat.com/show_bug.cgi?id=830177
[ 2 ] Bug #828354 - mdadm-takeover.service not removed on uninstallation
https://bugzilla.redhat.com/show_bug.cgi?id=828354
[ 3 ] Bug #820124 - RFE: Limit raid-check cron to a maximum number of concurrent checks
https://bugzilla.redhat.com/show_bug.cgi?id=820124
[ 4 ] Bug #822850 - mdadm-3.2.5 is available
https://bugzilla.redhat.com/show_bug.cgi?id=822850
[ 5 ] Bug #821717 - mdadm --add fails in common situations
https://bugzilla.redhat.com/show_bug.cgi?id=821717
[ 6 ] Bug #820527 - Update mdadm to version 3.2.4
https://bugzilla.redhat.com/show_bug.cgi?id=820527
[ 7 ] Bug #817023 - "mdadm --monitor" crashes when resync finishes
https://bugzilla.redhat.com/show_bug.cgi?id=817023
[ 8 ] Bug #817024 - imsm: validate the number of imsm volumes per controller
https://bugzilla.redhat.com/show_bug.cgi?id=817024
[ 9 ] Bug #817026 - mdadm: add volume's size expansion feature
https://bugzilla.redhat.com/show_bug.cgi?id=817026
[ 10 ] Bug #817028 - mdadm: imsm: second volume must have size of whole free space left on devices
https://bugzilla.redhat.com/show_bug.cgi?id=817028
[ 11 ] Bug #817029 - imsm: disk/volume sizes incorrect when using disks 1TB+
https://bugzilla.redhat.com/show_bug.cgi?id=817029
[ 12 ] Bug #817032 - link to imsm container device is not created when incremental assembly is used
https://bugzilla.redhat.com/show_bug.cgi?id=817032
[ 13 ] Bug #817038 - Can't add bitmap to array (version 1.0 metadata)
https://bugzilla.redhat.com/show_bug.cgi?id=817038
[ 14 ] Bug #808774 - make mdadm --add not do stupid things
https://bugzilla.redhat.com/show_bug.cgi?id=808774
[ 15 ] Bug #817039 - Rebuild does not continue after reboot.
https://bugzilla.redhat.com/show_bug.cgi?id=817039
[ 16 ] Bug #817042 - mdadm: Reset 'bad' flag on map update
https://bugzilla.redhat.com/show_bug.cgi?id=817042
[ 17 ] Bug #817522 - MD raid devices inactive after reboot done during reshape
https://bugzilla.redhat.com/show_bug.cgi?id=817522
[ 18 ] Bug #807743 - mdadm write intent map not functioning as before
https://bugzilla.redhat.com/show_bug.cgi?id=807743
--------------------------------------------------------------------------------
This update can be installed with the "yum" update program. Use
su -c 'yum update mdadm' at the command line.
For more information, refer to "Managing Software with yum",
available at http://docs.fedoraproject.org/yum/.
All packages are signed with the Fedora Project GPG key. More details on the
GPG keys used by the Fedora Project can be found at
https://fedoraproject.org/keys
--------------------------------------------------------------------------------
More information about the package-announce
mailing list