https://bugzilla.novell.com/show_bug.cgi?id=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c1 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |nfbrown@suse.com --- Comment #1 from Steffen Winterfeldt <snwint@suse.com> 2013-11-08 11:02:42 CET --- The issue is more that it is running without config. So I think it's a package issue. -- 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=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c3 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|per@computer.org | --- Comment #3 from Per Jessen <per@computer.org> 2013-11-11 08:19:40 UTC --- (In reply to comment #2)

It this a problem?

It is useful to have it running if any array is started.

It is easily disabled and stopped, so "problem" is perhaps a bit strong, but it certainly seems unnecessary unless arrays have been configured. I have long been in the habit of configuring and running mdadmd on machines with arrays, which is why I noticed mdadmd running on this machine which has no arrays (hardware raid).

I guess we could conceivably arrange to start it when any array was started. That would require deeper integration with systemd which I guess is inevitable.

Unless it is appropriately configured, the mails will go to root, which quite likely won't be read. Personally speaking, I feel it ought to be the admins job to configure and enable it and make sure the warnings go somewhere sensible. Purely my opinion though. -- 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=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c5 Per Jessen <per@computer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #5 from Per Jessen <per@computer.org> 2013-11-12 07:43:16 UTC --- (In reply to comment #4)

I just checked a new install of 13.1-rc and mdadmd is not enabled:

systemctl is-enabled mdadmd

reports

disabled

I guess it is conceivable that an upgrade does something different to a fresh install.

Are you sure that mdadmd wasn't enabled previously?

The box is for testing only, it has been running since around June with various 13.1 installations, plus updates. The first kernel was 3.10.0-rc4-1-default. mdadm was installed on the first install (from the y2logs). I would never have had reason to run mdadm on it, as it doesn't have any individual disks, only an HP Smartarray. Judging by the logs, the first start of mdadmd happens 3 October, after an update on 2 October. Kernel was updated to 3.11.2-1.g420e19b-default. I grep'ed around a bit: chestnut:/var/log/zypp # grep mdadm history # 2013-06-15 14:31:56 mdadm-3.2.6-6.2.x86_64.rpm installed ok # Updating /etc/sysconfig/mdadm... 2013-06-15 14:31:56|install|mdadm|3.2.6-6.2|x86_64||openSUSE-13.1-1.12|2230fac607d7140a2e43e174f0680ff53c3dd7ebe6d22e99a1ba1e8686e6491f| # 2013-08-09 17:02:38 mdadm-3.2.6-7.3.x86_64.rpm installed ok # Updating /etc/sysconfig/mdadm... # redirecting to systemctl try-restart mdadmd 2013-08-09 17:02:38|install|mdadm|3.2.6-7.3|x86_64||openSUSE-13.1-1.12|658ea2bc6a05437b4fcd145b59a01e462ccbc1df363be222a0bd0fbb0871aaf0| # 2013-08-21 13:38:47 mdadm-3.2.6-7.4.x86_64.rpm installed ok # Updating /etc/sysconfig/mdadm... # redirecting to systemctl try-restart mdadmd 2013-08-21 13:38:47|install|mdadm|3.2.6-7.4|x86_64||factory|9e3a52502c02c59ee7d9f7dd5560af5151cd4c694e3c248f754cb6c5f3b15fc1| # 2013-10-02 14:40:08 mdadm-3.3-5.2.x86_64.rpm installed ok # Updating /etc/sysconfig/mdadm... # redirecting to systemctl try-restart mdadmd 2013-10-02 14:40:08|install|mdadm|3.3-5.2|x86_64||factory|e52d93f721ab7caf6d81ea882d44da0d8b64f720e15abd88a91acf5cf4b5f5f3| -- 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=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c7 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #7 from Neil Brown <nfbrown@suse.com> 2013-12-11 04:19:21 UTC --- I plan to redo the way "mdadm --monitor" is started so that a systemd service is triggered whenever udev sees an md array come online. I think that should provide a clean solution here. I'll be a while before this hits Factory and it may not make it to 13.1, but I'll leave the bug open until it is all resolved as far as it can be. -- 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=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c9 --- Comment #9 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-01-23 01:00:19 CET --- This is an autogenerated message for OBS integration: This bug (849523) was mentioned in https://build.opensuse.org/request/show/214745 Factory / mdadm -- 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=849523 https://bugzilla.novell.com/show_bug.cgi?id=849523#c13 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|--- |13.2 Milestone 0 --- Comment #13 from Neil Brown <nfbrown@suse.com> 2014-02-18 01:25:06 UTC --- I'm marking this as fixes in 13.2. The mdadm in Factory does not have this problem as it starts "mdadm --monitor" a different way. This problem only seems to affect upgrades and I don't think there is an easy to way to "fix" it, or a great need. Thanks for the report. -- 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.