https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c kk zhang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@novell.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c2 --- Comment #2 from Valentin Birdeanu 2012-05-04 07:09:00 UTC --- Hello there, I've been hit by the same bug with Intel board with / and boot on a single RAID10 setup. I know that the people from systemd were commenting that this is to be expected on such a setup but my previous experience with similar setups was a good one. My systemd: systemd-37-3.11.1.x86_64 #uname -a 3.1.10-1.9-default #1 SMP Thu Apr 5 18:48:38 UTC 2012 (4a97ec8) x86_64 x86_64 x86_64 GNU/Linux The same thing happens also with halt or poweroff (I've read afterwards that the right command should be poweroff) and also by selecting poweroff / reboot from a kde session. This is rather bad since I've already lost a fresh install since the RAID was syncing at a shutdown. Is there any planned work for a patch or at least for a workaround like the ones from the redhat, e.g. by using SysRq ? Should I try to switch to systemV? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c4 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@suse.com AssignedTo|mmarek@suse.com |nfbrown@suse.com --- Comment #4 from Michal Marek 2012-06-18 13:52:23 UTC --- (In reply to comment #1)

Thanks for the link. The important bit is here:

https://bugzilla.redhat.com/show_bug.cgi?id=752593#c7 """ Intel BIOS RAID is the common pattern here. The problem is that Intel RAID is partially implemented in userspace (mdmonitor) and we kill all userspace processes before umounting. There's been a discussion about this on systemd-devel recently. The fix will be to stop doing the mdmon takeover on boot. Instead the mdmonitor running from initramfs will be kept alive all the time. On shutdown we won't kill it and umount/remount will succeed. """

I'm not sure if openSUSE behaves the same, but it's a start.

The initrd does not kill mdmon, this is done in /etc/init.d/boot.md. To test if the above approach can work, just uncomment the /sbin/mdmon --all --takeover calls in /etc/init.d/boot.md and reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c5 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #5 from Neil Brown 2012-08-20 07:08:20 UTC --- I have just submitted an update for Factory which I believe fixes this. As significant part of the fix is to add "--offroot" option to mdadm which ensures that systemd doesn't kill mdmon. Maintenance: will updates to Factory still flow to 12.2, or do I need to lodge and update request? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c7 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #7 from Neil Brown 2012-08-20 07:55:56 UTC --- Thanks Marcus, I've created maintenancerequest for 12.1 and 12.2. I tried 'osc patchinfo' and got: Current checked out package has no _patchinfo. Either call it from project level or specify patch name. So I tried: osc patching mdadm and got Creating new patchinfo... Server returned an error: HTTP Error 404: Not Found mdadm so decided to just go with 'osc maintenancerequest' and to fix up the mess when someone told me how to (Various documents didn't seem to give useful hints). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c9 --- Comment #9 from Marcus Meissner 2012-08-20 09:14:56 UTC --- neil, we will fix it up. :) osc patchinfo would only work if you used "osc mbranch" or "osc branch -M" before, not for regular branches. i checked the submits and they look good, there was one superflous for 12.2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=752107 https://bugzilla.novell.com/show_bug.cgi?id=752107#c11 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #11 from Neil Brown 2012-09-17 03:57:58 UTC --- I believe this has now been fixed. If the problem continues after the latest updates have been installed, please re-open. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.