[Bug 1279741] Re: Degraded array check, may not do what it says it's doing

Launchpad Bug Tracker 1279741 at bugs.launchpad.net
Tue Feb 18 17:03:16 UTC 2014


This bug was fixed in the package mdadm - 3.2.5-5ubuntu3

---------------
mdadm (3.2.5-5ubuntu3) trusty; urgency=medium

  * Drop precise-sru-reverts.patch, which disabled imsm/ddf raid assembly.
  * Take kernel cmdline parameters "nomdmonisw" and "nomdmonddf" into
    account, when assembling imsm/ddf arrays. This defaults to assembling
    those arrays using mdmon/mdadm, with a fallback to dmraid upon
    request.
  * Add breaks on dmraid, of versions that assemble fakeraid devices by
    default.
  * Drop degraded array questions, since the degraded check results in
    false negatives (e.g. all drives present & started arrays, yet
    resyncing) assemble arrays as best as is possible. (LP: #1279741)
  * Use default/grub.d snippet to continue using dmraid to assemble
    fakeraid arrays.
 -- Dimitri John Ledkov <xnox at ubuntu.com>   Tue, 18 Feb 2014 09:12:20 +0000

** Changed in: mdadm (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1279741

Title:
  Degraded array check, may not do what it says it's doing

Status in “mdadm” package in Ubuntu:
  Fix Released

Bug description:
  Degraded array check in the initramfs currently does:
  mdadm --misc --scan --detail --test

  and checks the return code. I happen to be using Intel Matrix Raid
  (container type), thus as it happens the container, and arrays are
  already assembled -> all arrays active, one disk active, one spare and
  rebuilding. At this state mdadm --misc --scan --detail --test returns
  error code 2, but it is to late to do anything but simply use that
  active array and continue to boot...

  So degraded_array question should die.

  We should attempt starting arrays with --no-degraded a few times, and
  after a timeout assemble them with --run, and if we don't have enough
  drives to start the array only then fall through to initramfs recovery
  shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1279741/+subscriptions



More information about the foundations-bugs mailing list