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

[Unit]
Description=Activate md array even though degraded
DefaultDependencies=no

[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`

			`[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`