Opened 9 years ago

Closed 9 years ago

#6781 closed enhancement (fixed)

mdadm-3.3.4

Reported by: Fernando de Oliveira Owned by: Fernando de Oliveira
Priority: high Milestone: 7.8
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

https://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-3.3.4.tar.xz

https://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-3.3.4.tar.sign

https://www.kernel.org/pub/linux/utils/raid/mdadm/ANNOUNCE

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.

Change History (3)

comment:1 by Fernando de Oliveira, 9 years ago

Owner: changed from blfs-book@… to Fernando de Oliveira
Status: newassigned

comment:2 by Fernando de Oliveira, 9 years ago

Test suite has run 122 tests.

I am considering to reword the tests text: some tests fail for unknown reasons.

Number of succeeded tests:
113

Number of FAILED tests:
9

FAILED tests:
tests/00raid1... FAILED
tests/02r1add... FAILED
tests/07autoassemble... FAILED
tests/07changelevels... FAILED
tests/07revert-grow... FAILED
tests/07revert-inplace... FAILED
tests/07revert-shrink... FAILED
tests/07testreshape5... FAILED
tests/10ddf-incremental-wrong-order... FAILED

But help is much appreciated. It will take at least 4 hours, before commit.

In order to run just the 9 failed for me tests, giving instructions below, because all 122 tests take over one hour or about 23 SBU.

After make:

make test

As root:

./test --keep-going --logdir=tests-logs --save-logs \
--tests=00raid1,02r1add,07autoassemble,07changelevels,07revert-grow,07revert-inplace,07revert-shrink,07testreshape5,10ddf-incremental-wrong-order

comment:3 by Fernando de Oliveira, 9 years ago

Resolution: fixed
Status: assignedclosed
  • Update to mdadm-3.3.4.
  • Update to swig-3.0.7.
  • Update to libsecret-0.18.3.
  • Update to gparted-0.23.0.
  • Update to mpg123-1.22.3.
  • Update to graphite2-1.3.0.
  • Update to unrar-5.3.2.
  • Some gcc5 tags.

Fixed at r16326.

Note: See TracTickets for help on using tickets.