]> git.ipfire.org Git - thirdparty/mdadm.git/blame - ANNOUNCE-3.2
DDF: compare_super_ddf: merge local info of other superblock
[thirdparty/mdadm.git] / ANNOUNCE-3.2
CommitLineData
a201e680
N
1Subject: ANNOUNCE: mdadm 3.2 - A tool for managing Soft RAID under Linux (DEVEL ONLY)
2
3I am pleased to announce the availability of
4 mdadm version 3.2
5
6It is available at the usual places:
7 countrycode=xx.
8 http://www.${countrycode}kernel.org/pub/linux/utils/raid/mdadm/
9and via git at
10 git://neil.brown.name/mdadm devel-3.2
11 http://neil.brown.name/git?p=mdadm
12
13This is a "Developers only" release. Please don't consider using it
14or making it available to others without reading the following.
15
16
17By far the most significant change in this release related to the
18management of reshaping arrays. This code has been substantially
19re-written so that it can work with 'externally managed metadata' -
20Intel's IMSM in particular. We now support level migration and
21OnLine Capacity Expansion on these arrays.
22
23However, while the code largely works it has not been tested
24exhaustively so there are likely to be problems. As the reshape code
25for native metadata arrays was changed as part of this rewrite these
26problems could also result in regressions for reshape of native
27metadata.
28
29It is partly to encourage greater testing that this release is being
30made. Any reports of problem - particular reproducible recipes for
31triggering the problems - will be gratefully received.
32
33It is hopped that a "3.2.1" release will be available in early March
34which will be a bugfix release over this and can be considered
35suitable for general use.
36
37Other changes of note:
38
39 - Policy framework.
40 Various policy statements can be made in the mdadm.conf to guide
41 the behaviour of mdadm, particular with regards to how new devices
42 are treated by "mdadm -I".
43 Depending on the 'action' associated with a device (identified by
44 its 'path') such need devices can be automatically re-added to and
45 existing array that they previously fell out off, or automatically
46 added as a spare if they appear to contain no data.
47
48 - mdadm now has a limited understanding of partition tables. This
49 allows the policy framework to make decisions about partitioned
50 devices as well.
51
52 - --incremental --remove can be told what --path the device was on,
53 and this info will be recorded so that another device appearing at
54 the same physical location can be preferentially added to the same
55 array (provides the spare-same-slot action policy applied to the
56 path).
57
58 - A new flags "--invalid-backup" flag is available in --assemble
59 mode. This can be used to re-assemble an array which was stopping
60 in the middle of a reshape, and for which the 'backup file' is no
61 longer available or is corrupted. The array may have some
62 corruption in it at the point where reshape was up to, but at least
63 the rest of the array will become available.
64
65
66 - Various internal restructuring - more is needed.
67
68
69Any feed back and bug reports are always welcomed at:
70 linux-raid@vger.kernel.org
71
72And please: don't use this in production - particularly not the
73--grow functionality.
74
75NeilBrown 1st February 2011
76
77