http://bugzilla.novell.com/show_bug.cgi?id=853944 http://bugzilla.novell.com/show_bug.cgi?id=853944#c7 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(883f6ce9@opayq.co | |m) | --- Comment #7 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Neil Brown from comment #6)
Can you please move the Conflicts= line from mdadm-last-resort@.timer to mdadm-last-resort@.service can confirm that this fixes the issues?
Doesn't look like it. boot dmesg | grep -i activ | grep -i degraded [ 88.912859] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.912894] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.912931] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.912963] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.912984] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.913001] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 119.419984] systemd[1]: Starting Activate md array even though degraded... [ 119.426709] systemd[1]: Starting Activate md array even though degraded... [ 119.435537] systemd[1]: Starting Activate md array even though degraded... [ 119.463533] systemd[1]: Started Activate md array even though degraded. [ 119.474120] systemd[1]: Started Activate md array even though degraded. [ 119.482104] systemd[1]: Started Activate md array even though degraded. cat /proc/mdstat | grep ^md | sort md0 : active raid1 sdf3[1] sde3[0] md1 : active raid1 sde4[0] sdf4[1] md2 : active raid10 sda1[1] sdc1[3] sdd1[2] sdb1[0] md3 : active raid10 sdm1[3] sdl1[0] sdn1[2] sdk1[1] md4 : active raid10 sdg1[0] sdh1[1] sdi1[2] sdj1[3] EDIT cat /usr/lib/systemd/system/mdadm-last-resort@.service [Unit] Description=Activate md array even though degraded DefaultDependencies=no + Conflicts=sys-devices-virtual-block-%i.device [Service] Type=oneshot ExecStart=/sbin/mdadm --run /dev/%i cat /usr/lib/systemd/system/mdadm-last-resort@.timer [Unit] Description=Timer to wait for more drives before activating degraded array. DefaultDependencies=no - Conflicts=sys-devices-virtual-block-%i.device [Timer] OnActiveSec=30 reboot dmesg | grep -i activ | grep -i degraded [ 88.693704] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.693721] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.693729] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.693742] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 88.693748] systemd[1]: Starting Timer to wait for more drives before activating degraded array.. [ 88.693761] systemd[1]: Started Timer to wait for more drives before activating degraded array.. [ 118.779355] systemd[1]: Starting Activate md array even though degraded... [ 118.790671] systemd[1]: Starting Activate md array even though degraded... [ 118.801642] systemd[1]: Starting Activate md array even though degraded... [ 118.850604] systemd[1]: Started Activate md array even though degraded. [ 118.856927] systemd[1]: Started Activate md array even though degraded. [ 118.864238] systemd[1]: Started Activate md array even though degraded. -- You are receiving this mail because: You are on the CC list for the bug.