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

Darin Avery darin.avery at gmail.com
Mon Feb 1 02:01:57 UTC 2016


This problem just started happening for me too.  I tried only the
changes in #13 but it still resyncs.  Are the changes in 12 necessary as
well?

I tried the pidof command on its own and got this: "sed: -e expression
#2, char 9: unterminated `s' command"


Also ps ax|grep mdmon shows nothing, and mdmon /dev/md0 gives "mdmon: md0 is not a container - cannot monitor" so it's not clear to me when, if ever, mdmon is running or how to make it run.

1. Is mdmon supposed to be running all the time?
2. Does this work for an mdadm array on any hardware, or only intel?  (imsm means intel matrix storage, correct?)

In case anyone else is having this, instead of shutting down, try
suspend.  That doesn't trigger the resync for me.

Thanks.

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



More information about the foundations-bugs mailing list