multipathd.service can start up and run just fine without blk-availability.service. It is only necessary to coordinate shutdown order in certain multipath setups (over iscsi for instance). Thus, instead of "Requires", multipathd.service should use "Wants"
Signed-off-by: Benjamin Marzinski <bmarz...@redhat.com> --- multipathd/multipathd.service | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/multipathd/multipathd.service b/multipathd/multipathd.service index fc2e009..d5f8606 100644 --- a/multipathd/multipathd.service +++ b/multipathd/multipathd.service @@ -1,11 +1,10 @@ [Unit] Description=Device-Mapper Multipath Device Controller -Requires=blk-availability.service Before=iscsi.service iscsid.service lvm2-activation-early.service Before=local-fs-pre.target After=multipathd.socket DefaultDependencies=no -Wants=local-fs-pre.target multipathd.socket +Wants=local-fs-pre.target multipathd.socket blk-availability.service Conflicts=shutdown.target [Service] -- 1.8.3.1 -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel
