Bug 756336 - Migration to RAID5 is sometimes not possible (memory leak)
Summary: Migration to RAID5 is sometimes not possible (memory leak)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mdadm
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jes Sorensen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 755005
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-23 10:34 UTC by Jes Sorensen
Modified: 2011-12-14 23:36 UTC (History)
6 users (show)

Fixed In Version: mdadm-3.2.2-15.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of: 755005
Environment:
Last Closed: 2011-12-14 23:36:57 UTC
Type: ---


Attachments (Terms of Use)

Description Jes Sorensen 2011-11-23 10:34:12 UTC
+++ This bug was initially created as a clone of Bug #755005 +++

Migration from Non-RAID system to RAID5 may sometimes be not possible. There is
a memory leak in mdadm which may stop the migration process. This occurs
especially when large disks are used.

There is a fix:
http://neil.brown.name/git?p=mdadm;a=commitdiff;h=758be4f1c9cda8eefb2fd241835521462196e16c

Originally reported by Maciej Patelczyk

Comment 1 Fedora Update System 2011-11-23 10:49:12 UTC
mdadm-3.2.2-15.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/mdadm-3.2.2-15.fc15

Comment 2 Fedora Update System 2011-11-23 23:30:10 UTC
Package mdadm-3.2.2-15.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mdadm-3.2.2-15.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16322/mdadm-3.2.2-15.fc15
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-12-14 23:36:57 UTC
mdadm-3.2.2-15.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.