[Bug 1320402] Re: mdadm resyncs imsm raid in "Normal" state

[MatthewHawn]

Comment #12 worked for me! Thanks Chris.mn.

However, I believe the more canonical way of omitting the PIDs to kill
would be to use the /run/sendsigs.omit.d directory.  Interestingly,
/etc/init.d/mdadm already adds mdmon to this, just only on stop, not
start. I don't understand why and this may be a mistake.

In any case,  I have attached a patch to /etc/init.d/mdadm that adds the
mdmon PID to the sendsigsomit.d directory on start.

The check_raid in umountroot is also needed for me and I have included
that in the patch

** Patch added: "mdadm.patch"
   https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/+attachment/4270840/+files/mdadm.patch

-- 
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/1320402

Title:
   mdadm resyncs imsm raid in "Normal" state

Status in mdadm package in Ubuntu:
  Confirmed

Bug description:
  Got an imsm raid1 which I don't boot from. Whenever bios reports the
  raid as being in "Normal" state, mdadm starts a resync of it after
  boot. If a resync already is underway (bios reports it as being in
  "Verify" state), it continues where it left off.

  This appears to be very similar to a problem in Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=753335 It's apparently
  fixed there for some time now. (The workaround mentioned in comment 41
  in that ticket doesn't work in Ubuntu, but I guess that's due to
  distro differences in initramfs and systemd.)

  Using mdadm 3.2.5-5ubuntu4 in a fresh Trusty install.

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