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

[Martin Stjernholm]

#34 worked for me for all of about two weeks or so, then no more. I
suspect an update, but I couldn't find any update of any package that
seemed relevant.

I've now resorted to my first workaround in #8, i.e. to mount and
unmount the raid partitions separately from the ordinary boot and
shutdown process. That of course only works when the raid filesystems
aren't used during boot.

Since upstart is gone I converted my workaround to an old-school init.d
script, which works with systemd. I've attached it in case it helps
someone, but note that MDDEV and MOUNTS will need to be changed for the
local configuration.

While trying the script manually, I did notice that umount sometimes
failed due to filesystem being busy. I couldn't find any process with
open files though, and during shutdown such things should be cleaned up
earlier anyway. Might be a hint for this latest failure.

I usually stick to technical issues in bug reports, but I have to say
that this problem has gotten quite tedious and the lack of action - even
for an open source project - is disappointing.

** Attachment added: "init.d script to mount and unmount imsm raid separately"
   https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/+attachment/4751878/+files/local-mountraid

-- 
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
Status in mdadm package in Fedora:
  Unknown

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