From 69818a5c75ba5982e9d866f94239a2f5975f988e Mon Sep 17 00:00:00 2001 From: NeilBrown Date: Mon, 3 Aug 2015 16:17:13 +1000 Subject: [PATCH] Release mdadm-3.3.4 Important bugfix release. Signed-off-by: NeilBrown --- ANNOUNCE-3.3.4 | 37 +++++++++++++++++++++++++++++++++++++ ReadMe.c | 4 ++-- inventory | 1 + mdadm.8.in | 2 +- mdadm.spec | 2 +- mdassemble.8 | 2 +- mdmon.8 | 2 +- 7 files changed, 44 insertions(+), 6 deletions(-) create mode 100644 ANNOUNCE-3.3.4 diff --git a/ANNOUNCE-3.3.4 b/ANNOUNCE-3.3.4 new file mode 100644 index 00000000..52b94562 --- /dev/null +++ b/ANNOUNCE-3.3.4 @@ -0,0 +1,37 @@ +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. diff --git a/ReadMe.c b/ReadMe.c index 8af8cd0f..386d7a01 100644 --- a/ReadMe.c +++ b/ReadMe.c @@ -25,10 +25,10 @@ #include "mdadm.h" #ifndef VERSION -#define VERSION "3.3.3" +#define VERSION "3.3.4" #endif #ifndef VERS_DATE -#define VERS_DATE "24th July 2015" +#define VERS_DATE "3rd August 2015" #endif char Version[] = "mdadm - v" VERSION " - " VERS_DATE "\n"; diff --git a/inventory b/inventory index 36f2e942..a9fc3c01 100755 --- a/inventory +++ b/inventory @@ -21,6 +21,7 @@ ANNOUNCE-3.3 ANNOUNCE-3.3.1 ANNOUNCE-3.3.2 ANNOUNCE-3.3.3 +ANNOUNCE-3.3.4 Assemble.c Build.c COPYING diff --git a/mdadm.8.in b/mdadm.8.in index 912ee4c4..c25ac6c7 100644 --- a/mdadm.8.in +++ b/mdadm.8.in @@ -5,7 +5,7 @@ .\" the Free Software Foundation; either version 2 of the License, or .\" (at your option) any later version. .\" See file COPYING in distribution for details. -.TH MDADM 8 "" v3.3.3 +.TH MDADM 8 "" v3.3.4 .SH NAME mdadm \- manage MD devices .I aka diff --git a/mdadm.spec b/mdadm.spec index b5e0b694..293cb190 100644 --- a/mdadm.spec +++ b/mdadm.spec @@ -1,6 +1,6 @@ Summary: mdadm is used for controlling Linux md devices (aka RAID arrays) Name: mdadm -Version: 3.3.3 +Version: 3.3.4 Release: 1 Source: http://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-%{version}.tar.gz URL: http://neil.brown.name/blog/mdadm diff --git a/mdassemble.8 b/mdassemble.8 index 9a009389..7601b1aa 100644 --- a/mdassemble.8 +++ b/mdassemble.8 @@ -1,5 +1,5 @@ .\" -*- nroff -*- -.TH MDASSEMBLE 8 "" v3.3.3 +.TH MDASSEMBLE 8 "" v3.3.4 .SH NAME mdassemble \- assemble MD devices .I aka diff --git a/mdmon.8 b/mdmon.8 index 86fbb150..beb82e03 100644 --- a/mdmon.8 +++ b/mdmon.8 @@ -1,5 +1,5 @@ .\" See file COPYING in distribution for details. -.TH MDMON 8 "" v3.3.3 +.TH MDMON 8 "" v3.3.4 .SH NAME mdmon \- monitor MD external metadata arrays -- 2.39.2