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

[Martin Stjernholm]

I deviced a workaround for this by mounting and unmounting my raid
separately. The key is that I don't need it during boot, nor start any
daemons that keep files open on it.

First, I added the "noauto" option to all the mounts on the raid in
/etc/fstab.

Then I added an upstart script as below. Note that the raid device and
the mount points are hardcoded, so anyone using this needs to adapt
them. It also doesn't hook into plymouth (aka bootsplash) like the
normal mountall stuff does, so there aren't any nice messages and
prompts if the mounts fail.

/etc/init/local-mountraid.conf:

description "Mount the imsm raid separately to work around LP #1320402"

start on filesystem
stop on runlevel [!23]
task

post-start script
    mdadm --assemble /dev/md/vol0 || :
    mount /more
    mount /d
end script

post-stop script
    umount /d
    umount /more
    mdadm --stop /dev/md/vol0
end script

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