mdadm/systemd/mdadm-last-resort@.service

[Unit]
Description=Activate md array even though degraded
DefaultDependencies=no
Conflicts=sys-devices-virtual-block-%i.device

[Service]
Type=oneshot
ExecStart=BINDIR/mdadm --run /dev/%i
Systemd integration for starting newly-degraded arrays. Normally "mdadm -I" will not start an array if it has reason to expect further devices. This means that if a device is removed while the host is shut down, "mdadm -I" will never start the device. If the array is know to the host, it make sense to start the array anyway after a reasonable timeout. This patch adds systemd/udev infrastructure so that 30 seconds after a known array first becomes able to be assembled as a degraded array, the array will be assembled even if more devices are still expected. Signed-off-by: NeilBrown <neilb@suse.de> 2013-12-02 06:08:04 +01:00			`[Unit]`
			`Description=Activate md array even though degraded`
			`DefaultDependencies=no`
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> 2016-01-28 01:45:53 +01:00			`Conflicts=sys-devices-virtual-block-%i.device`
Systemd integration for starting newly-degraded arrays. Normally "mdadm -I" will not start an array if it has reason to expect further devices. This means that if a device is removed while the host is shut down, "mdadm -I" will never start the device. If the array is know to the host, it make sense to start the array anyway after a reasonable timeout. This patch adds systemd/udev infrastructure so that 30 seconds after a known array first becomes able to be assembled as a degraded array, the array will be assembled even if more devices are still expected. Signed-off-by: NeilBrown <neilb@suse.de> 2013-12-02 06:08:04 +01:00
			`[Service]`
			`Type=oneshot`
install: use BINDIR consistently to locate mdadm and mdmon Every place where the paths for mdadm or mdmon is explicit, it should use the BINDIR setting, not "/sbin/". Reported-by: member graysky <graysky@archlinux.us> (https://bugs.archlinux.org/task/37330) Signed-off-by: NeilBrown <neilb@suse.de> 2014-05-22 09:13:02 +02:00			`ExecStart=BINDIR/mdadm --run /dev/%i`