diff options
author | NeilBrown <neilb@suse.com> | 2016-01-28 11:45:53 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.com> | 2016-01-28 11:45:53 +1100 |
commit | cec72c071bbec386383ec64d25826c4f421efbc0 (patch) | |
tree | b1c32b2b7acfc39c9b6ccfa4b1ffd6fd0ebfd582 /systemd | |
parent | ac92b44a8736071fef61116d04b4e1bfebee30ab (diff) | |
download | mdadm-cec72c071bbec386383ec64d25826c4f421efbc0.tar.gz |
systemd/mdadm-last-resort: add Conflicts to .service file.
It seems that having the Conflicts in the .timer file is not sufficient.
Sometimes it works, but if the timer gets requested after the conflicting
block device appears (or was it "before" ...) the timer is not aborted.
Having the Conflicts in both files seems to work reliably.
URL: https://bugzilla.suse.com/show_bug.cgi?id=853944
Signed-off-by: NeilBrown <neilb@suse.com>
Diffstat (limited to 'systemd')
-rw-r--r-- | systemd/mdadm-last-resort@.service | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/systemd/mdadm-last-resort@.service b/systemd/mdadm-last-resort@.service index 5179f19..e93d72b 100644 --- a/systemd/mdadm-last-resort@.service +++ b/systemd/mdadm-last-resort@.service @@ -1,6 +1,7 @@ [Unit] Description=Activate md array even though degraded DefaultDependencies=no +Conflicts=sys-devices-virtual-block-%i.device [Service] Type=oneshot |