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

[Roger Lawhorn]

I have tried two different fixes for this (#12 and #13).
It won't stop.
At this point I can no longer use raid at all.
If my boot drive was raid 5 I'd be screwed as I could not turn it off at all.
I use raid 1 so I am lucky.

Can someone post a command to FORCE the raid to be clean?
Perhaps a forced immediate sync?
The 'mdadm --wait-clean --scan' only tells mdadm to do it as soon as possible.
It does not work either.

I have resorted to running ">echo 5000 >
/proc/sys/dev/raid/speed_limit_max" on boot to gain control of my
machine back. It slows the resync to 5mb/sec instead of 120mb/sec.
However, with this temp fix I never have a full raid mirror backup.

I use my machine to do real work.
This is beyond unbearable and unthinkable that this bug has no cure yet.

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