For anyone else, 3.1.5 is what you want.ģ.2.1 should be released soonish. For people who want to use the Intel metadata format (Intel Matrix Storage Manager - IMSM) on Intel motherboards which have BIOS support and MS-Windows support, you should probably wait for 3.2.1. This avoids inadvertently turningĭevices into spares when an array is failed.Īs you can see - lots of little bits and pieces.
It is essentially 3.1.4 plus all the bug fixes found while working on 3.2 and 3.2.1. That's OK though as I keep the release announcements in the source distribution so you can always go and read them there.ģ.1.5 is just bugfixes. As I am now announcing 3.1.5 you can see that I missed a few. The last release of mdadm that I mentioned in this blog was 2.6.1. It should work fine and is no more likely to eat your data than any other program out there.Ģ3 March 2011, 04:59 UTC Release of mdadm-3.1.5 But if you are at all interested in the new functionality, then by all means give 3.2.1 a try. If you don't want any of the new functionality then it is probably safest to stay with 3.1.5 as it has all recent bug fixes.
In particular if you start a reshape in Linux and then shutdown and boot into Window, the Windows driver may not correctly restart the reshape. This support is not quite complete yet and requires MDADM_EXPERIMENTAL=1 in the environment to ensure people only use it with care. Spare migration is now possible as is level migration and OLCE (OnLine Capacity Expansion). Secondly, the support for Intel Matrix Storage Manager (IMSM) arrays has been substantially enhanced. It is likely that more functionality will be added to this framework over time It also allows broader controller of spare-migration between arrays. when a device is hot-plugged it can immediately be made a hot-spare for an array without further operator intervention. This allows us to set policy for different devices based on where they are connected (e.g.
The 3.2 series contains two particular sets of new functionality.įirstly there is the "policy" framework. Hot on the heals of mdadm-3.1.5 I have just released 3.2.1. Useful to write up some thoughts more coherently and completely.Ģ8 March 2011, 02:54 UTC Another mdadm release: 3.2.1 I recently had some interest shown in this so I thought it might be
In an answer to a comment on a blog post: Over a year ago I wrote some thoughts about closing the RAID5 write hole
You most likely will never need use the output of that command, but if youġ4 June 2011, 10:17 UTC Closing the RAID5 write hole To do is read to the end of this note and then proceed accordingly. Should do (after not panicking) is to gather the output ofĪnd save this somewhere that is not on a RAID array.
If you are concerned that this might affect you, the first thing you It won't destroy your data, but it could make it hard There is a rather nasty RAID bug in some released versions of the But I can't really know unless I record it, then compare it with future weeks.ġ5 June 2012, 07:32 UTC A Nasty md/raid bug So what has happened this week? I doubt it is really a typical week as no week is really typical - I imagine them all outside my window screaming in chorus "We are all individuals". But I think I should try to push through that. I sometime feel unwilling to write unless I'll say something to amaze the whole Internet. To posterity with all the eclat of a proverb. Something that will amaze the whole room, and be handed down Taciturn disposition, unwilling to speak, unless we expect to say