I can confirm that if the raid stays in auto-read-only state (i.e. isn't written to), then it won't start a resync on the next boot. I verified that by not mounting any of the file systems (for me it's enough to mount a file system to cause a write - it doesn't have to be a file write). That being the case, is there any significant difference from your case, dam-brouard?
Also, if I stop the raid and the container manually before reboot, it stays clean on the next boot as well. I found this Gentoo bug which is similar as well: https://bugs.gentoo.org/show_bug.cgi?id=395203 It pointed out that mdmon should be kept running during the shutdown to write out the external metadata after the raid is stopped. So I tried a similar fix in /etc/init.d/killprocs to spare any mdmon processes. That didn't help, but I haven't verified that mdmon is kept running long enough - it could be a necessary but not sufficient fix. ** Bug watch added: Gentoo Bugzilla #395203 https://bugs.gentoo.org/show_bug.cgi?id=395203 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320402 Title: mdadm resyncs imsm raid in "Normal" state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
