mdadm/systemd/mdadm.shutdown

#!/bin/sh
# We need to ensure all md arrays with external metadata
# (e.g. IMSM, DDF) are clean before completing the shutdown.
BINDIR/mdadm --wait-clean --scan
systemd: various fixes for boot with container-arrays. 1/ Add systemd shutdown script to ensure DDF and IMSM are clean before we actually shutdown 2/ Get udev to tell systemd to run the mdmon@mdXXX.service units when a member array appears. If we boot off a member array (with dracut at least), the mdmon started in the initramfs will lose track of /sys etc, so we need to restart it. systemd will try to forget about it too (but not actually kill it because we said not to do this). Having udev tell it to start it will allow a new mdmon to run which can see /sys, and systemd will know about it. 3/ Always use --offroot and --takeover when starting mdmon with systemd --offroot is needed else shutdown will hang. --takeover is needed incase an mdmon was started earlier (e.g. in initramfs). Neither hurt if they aren't actually needed. Signed-off-by: NeilBrown <neilb@suse.de> 2014-04-08 09:22:18 +02:00			`#!/bin/sh`
			`# We need to ensure all md arrays with external metadata`
			`# (e.g. IMSM, DDF) are clean before completing the shutdown.`
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			`BINDIR/mdadm --wait-clean --scan`