FM / mdadm

/usr/share/doc/mdadm

Name	Size	Mode	Actions
examples/	-	0755	rm
ANNOUNCE-3.0	3486	0644	edit dl rm
ANNOUNCE-3.0.1	620	0644	edit dl rm
ANNOUNCE-3.0.2	583	0644	edit dl rm
ANNOUNCE-3.0.3	1009	0644	edit dl rm
ANNOUNCE-3.1	1164	0644	edit dl rm
ANNOUNCE-3.1.1	1442	0644	edit dl rm
ANNOUNCE-3.1.2	1795	0644	edit dl rm
ANNOUNCE-3.1.3	1933	0644	edit dl rm
ANNOUNCE-3.1.4	1332	0644	edit dl rm
ANNOUNCE-3.1.5	1792	0644	edit dl rm
ANNOUNCE-3.2	3014	0644	edit dl rm
ANNOUNCE-3.2.1	3313	0644	edit dl rm
ANNOUNCE-3.2.2	1546	0644	edit dl rm
ANNOUNCE-3.2.3	810	0644	edit dl rm
ANNOUNCE-3.2.4.gz	3696	0644	edit dl rm
ANNOUNCE-3.2.5	1046	0644	edit dl rm
ANNOUNCE-3.2.6	2664	0644	edit dl rm
ANNOUNCE-3.3	2752	0644	edit dl rm
ANNOUNCE-3.3.1	826	0644	edit dl rm
ANNOUNCE-3.3.2	467	0644	edit dl rm
ANNOUNCE-3.3.3	577	0644	edit dl rm
ANNOUNCE-3.3.4	1518	0644	edit dl rm
ANNOUNCE-3.4	888	0644	edit dl rm
ANNOUNCE-4.0	852	0644	edit dl rm
ANNOUNCE-4.1	551	0644	edit dl rm
changelog.Debian.gz	1833	0644	edit dl rm
copyright	885	0644	edit dl rm
external-reshape-design.txt.gz	4932	0644	edit dl rm
FAQ.gz	9907	0644	edit dl rm
mdmon-design.txt.gz	2561	0644	edit dl rm
NEWS.Debian.gz	2172	0644	edit dl rm
README.checkarray	1667	0644	edit dl rm
README.recipes.gz	1905	0644	edit dl rm
TODO.Debian	1238	0644	edit dl rm
TODO.gz	3097	0644	edit dl rm

Edit: /usr/share/doc/mdadm/ANNOUNCE-3.3.4 (1518B)

Subject: ANNOUNCE: mdadm 3.3.4 - A tool for managing md Soft RAID under Linux

I am somewhat disappointed to have to announce the availability of
   mdadm version 3.3.4

It is available at the usual places:
   http://www.kernel.org/pub/linux/utils/raid/mdadm/
and via git at
   git://github.com/neilbrown/mdadm
   git://neil.brown.name/mdadm
   http://git.neil.brown.name/git/mdadm.git

In mdadm-3.3 a change was made to how IMSM (Intel Matrix Storage
Manager) metadata was handled.  Previously an IMSM array would only
be assembled if it was attached to an IMSM controller.

In 3.3 this was relaxed as there are circumstances where the
controller is not properly detected.  Unfortunately this has negative
consequences which have only just come to light.

If you have an IMSM RAID1 configured and then disable RAID in the
BIOS, the metadata will remain on the devices.  If you then install
some other OS on one device and then install Linux on the other, Linux
might eventually start noticing the IMSM metadata (depending a bit on whether
mdadm is included in the initramfs) and might start up the RAID1.  This could
copy one device over the other, thus trashing one of the installations.

Not good.

So with this release IMSM arrays will only be assembled if attached to
an IMSM controller, or if "--force" is given to --assemble, or if the
environment variable IMSM_NO_PLATFORM is set (used primarily for
testing).

I strongly recommend upgrading to 3.3.4 if you are using 3.3 or later.

NeilBrown 3rd August 2015.

Subject: ANNOUNCE: mdadm 3.3.4 - A tool for managing md Soft RAID under Linux I am somewhat disappointed to have to announce the availability of mdadm version 3.3.4 It is available at the usual places: http://www.kernel.org/pub/linux/utils/raid/mdadm/ and via git at git://github.com/neilbrown/mdadm git://neil.brown.name/mdadm http://git.neil.brown.name/git/mdadm.git In mdadm-3.3 a change was made to how IMSM (Intel Matrix Storage Manager) metadata was handled. Previously an IMSM array would only be assembled if it was attached to an IMSM controller. In 3.3 this was relaxed as there are circumstances where the controller is not properly detected. Unfortunately this has negative consequences which have only just come to light. If you have an IMSM RAID1 configured and then disable RAID in the BIOS, the metadata will remain on the devices. If you then install some other OS on one device and then install Linux on the other, Linux might eventually start noticing the IMSM metadata (depending a bit on whether mdadm is included in the initramfs) and might start up the RAID1. This could copy one device over the other, thus trashing one of the installations. Not good. So with this release IMSM arrays will only be assembled if attached to an IMSM controller, or if "--force" is given to --assemble, or if the environment variable IMSM_NO_PLATFORM is set (used primarily for testing). I strongly recommend upgrading to 3.3.4 if you are using 3.3 or later. NeilBrown 3rd August 2015.