mdadm 3.2.5 - Changelog

What's new in mdadm 3.2.1:

March 28th, 2011

· Firstly there is the "policy" framework. This allows us to set policy for different devices based on where they are connected (e.g. which controller) so that e.g. when a device is hot-plugged it can immediately be made a hot-spare for an array without further operator intervention. It also allows broader controller of spare-migration between arrays. It is likely that more functionality will be added to this framework over time
· Secondly, the support for Intel Matrix Storage Manager (IMSM) arrays has been substantially enhanced. Spare migration is now possible as is level migration and OLCE (OnLine Capacity Expansion). This support is not quite complete yet and requires MDADM_EXPERIMENTAL=1 in the environment to ensure people only use it with care. 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. And vice-versa.

What's new in mdadm 3.1.5:

March 23rd, 2011

Two fixes related to configs that aren't using udev:
· Don't remove md devices which 'standard' names on --stop
· Allow dev_open to work on read-only /dev

And fixed regressions:
· Allow --incremental to add spares to an array
· Accept --no-degraded as a deprecated option rather than throwing an error
· Return correct success status when --incrmental assembling a container which does not yet have enough devices.
· Don't link mdadm with pthreads, only mdmon needs it.
· Fix compiler warning due to bad use of snprintf

What's new in mdadm 3.1.1:

March 26th, 2010

· Multiple fixes for new --grow levels including fixes for serious data corruption problems.
· Change default metadata to v1.1
· Change default chunk size to 512K
· Change default bitmap chunk size to 64Meg
· When --re-add is used, don't fall back to--add if --re-add fails as this can destroy data.