Red Hat Bugzilla – Bug 964172
dmraid should not be running in the default boot
Last modified: 2013-12-10 07:20:10 EST
Currently, "dmraid" is pulled into the boot process on all installations. Since dmraid pulls in udev-settle this causes major slow-down for most boots - for functionality only a small minority actually use.
We really should find a way to get this out of the boot. Hans de Goede suggested the following solution:
I also filed this bug to get dmraid not even installed from anaconda:
But since that won't solve the problems for livecds we still need that dmraid uses a condition check to get skipped when it isn't needed, the way Hans suggested in the mail above.
(In reply to comment #0)
> Currently, "dmraid" is pulled into the boot process on all installations.
> Since dmraid pulls in udev-settle this causes major slow-down for most boots
> - for functionality only a small minority actually use.
> We really should find a way to get this out of the boot. Hans de Goede
> suggested the following solution:
Hans' solution copes with temporary unavailable RAID sets as well, so yes, looks good to me.
Conditions are evaluated just before starting the service, so that won't prevent the pulling in of the udev-settle dependency, will it?
Heinz, relying on udev-settle is really broken. It's a broken concept and delays the boot for quite some time. Any chance this can be fixed? dm-raid should act as soon as devices show up rather then assume it is invoked after all devices have shown. Which is a point in time which doesn't even exist...
*** Bug 1039781 has been marked as a duplicate of this bug. ***
dmraid is not installed for normal installations by default any more, so it's not a general issue.
Users should disable the service on live systems if they don't use dmraid supported RAID sets at all.
On live media dmraid can be used conditionally outside the scope of systemd if it's required to support an installation destionation.