Per Jessen wrote:

I've just upgraded a box running 13.1M4 to RC2 - before I did so, I noticed that mdadm was running, for some strange reason. So I stopped and disabled it. After upgrading (zypper up), mdadm was back up and running, despite:

# systemctl status mdadm.service mdadm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

Hmm, can't stop it either: # systemctl stop mdadm Failed to issue method call: Unit mdadm.service not loaded. # systemctl stop mdadm.service Failed to issue method call: Unit mdadm.service not loaded. -- Per Jessen, Zürich (12.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2013-11-07 09:18 (GMT+0100) Per Jessen composed:

I guess mdadm is a pretty critical component :-), but do I really need to rename the binary to prevent it being started?

Maybe blacklist it out of initrd to keep it from loading. Locking it out should allow use of a RAID mirror disk as a regular disk, in case you ever need that. :-p If mkinitrd made your initrd you might try a switch to dracut, which I hear defaults to a hostonly option that leaves unneeded components out. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le jeudi 07 novembre 2013 à 09:48 +0100, Jan Engelhardt a écrit :

On Thursday 2013-11-07 09:12, Per Jessen wrote:

...

I've just upgraded a box running 13.1M4 to RC2 - before I did so, I noticed that mdadm was running, for some strange reason. So I stopped and disabled it. After upgrading (zypper up), mdadm was back up and running, despite:

# systemctl status mdadm.service mdadm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

Well, there is no service. Whatever you see must have been "manually" started (shell script, or whatever else). But what exactly is it that is running? Is it perhaps mdadmd rather than mdadm?

Or other initscripts / service file is referencing mdadm service / initscript, which doesn't exist. -- Frederic Crozat SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Jan Engelhardt wrote:

On Thursday 2013-11-07 09:12, Per Jessen wrote:

...

I've just upgraded a box running 13.1M4 to RC2 - before I did so, I noticed that mdadm was running, for some strange reason. So I stopped and disabled it. After upgrading (zypper up), mdadm was back up and running, despite:

# systemctl status mdadm.service mdadm.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

Well, there is no service. Whatever you see must have been "manually" started (shell script, or whatever else). But what exactly is it that is running? Is it perhaps mdadmd rather than mdadm?

Yup, you're right: # systemctl status mdadmd mdadmd.service - LSB: mdadmd daemon monitoring MD devices Loaded: loaded (/etc/init.d/mdadmd) Active: inactive (dead) since Thu 2013-11-07 09:18:25 CET; 1h 57min ago Process: 2382 ExecStop=/etc/init.d/mdadmd stop (code=exited, status=0/SUCCESS) Process: 2142 ExecStart=/etc/init.d/mdadmd start (code=exited, status=0/SUCCESS) Nov 07 09:04:01 chestnut systemd[1]: Starting LSB: mdadmd daemon monitoring MD devices... Nov 07 09:04:02 chestnut mdadmd[2142]: Starting mdadmd ..done Nov 07 09:04:02 chestnut systemd[1]: Started LSB: mdadmd daemon monitoring MD devices. Nov 07 09:18:25 chestnut mdadmd[2382]: Shutting down mdadmd ..done In the above, I had renamed the binary, so the LSB script wouldn't find it. I'm guessing that I left out a 'd' when I disabled too. Interstingly, systemctl doesn't complain: # systemctl disable mdadm.sercvice # systemctl disable mdadm.sercvice99 Doesn't seem to mind. (surely an error message would not go amiss here?) # systemctl disable mdadmd mdadmd.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig mdadmd off I'm not sure why mdadmd was installed by default, but maybe it's not such a bad choice. -- Per Jessen, Zürich (15.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Yamaban wrote:

On Thu, 7 Nov 2013 11:19, Per Jessen wrote:

...

Jan Engelhardt wrote:

...

On Thursday 2013-11-07 09:12, Per Jessen wrote: [snip] I'm not sure why mdadmd was installed by default, but maybe it's not such a bad choice.

Background: Package mdadmd is installed as a dependency of package libstorage4, which is dependency by autoyast and yast-backup

BUT, using "rm $(rpm -ql mdadmd)" (just removing the files, same as "rpm --install --justdb mdadmd" ), calling mkinitrd / dracut -H, rebooting, and using yast shows that the package is indeed NOT needed on systems with no raid.

Just "libstorage4" forces it on everybody regardless.

You want to change that? -> yast-devel list is your contact.

I do think it only ought to be installed when actually _needed_. Maybe I'll open a bugreport. -- Per Jessen, Zürich (17.3°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Jan Engelhardt wrote:

On Thursday 2013-11-07 11:19, Per Jessen wrote:

...

# systemctl status mdadmd mdadmd.service - LSB: mdadmd daemon monitoring MD devices Process: 2142 ExecStart=/etc/init.d/mdadmd start (code=exited, status=0/SUCCESS)

I'm not sure why mdadmd was installed by default, but maybe it's not such a bad choice.

Well, I would concur on that any normal user should be getting mail(*) about arrays changing abnormally (such as when devices fail) in the background.

Agree 100%, although it seems superfluous when there is no software RAID array to monitor. On the system I'm testing on here, there isn't even a /etc/mdadmd.conf file :-) -- Per Jessen, Zürich (16.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Thursday, 2013-11-07 at 13:28 +0100, Per Jessen wrote:

...

I do think it only ought to be installed when actually _needed_. Maybe I'll open a bugreport.

Well... I have btrfs tools and the cron job running everywhile, even though I have no btrfs partition on this system.

I don't have any of those. Minimal install.

On the other hand, xfs tools are installed on a separate package, and perhaps also reiserfs.

It is a similar issue :-)

I don't mind mdadm being installed, but it doesn't need to be running as a daemon when there is nothing to monitor. I wouldn't a superfluous cron-job either. -- Per Jessen, Zürich (10.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org