From 9161308252336491a107983ed16481e446853e26 Mon Sep 17 00:00:00 2001 From: Peter Rajnoha Date: Thu, 26 Jul 2012 11:30:27 +0200 Subject: systemd: ensure monitoring is handled after lvmetad Monitoring is handled using "vgchange --monitor" call. Ensure that lvmetad is up and running at the time of this call to prevent any fallback to direct scan within the vgchange. The same applies for shutdown sequence but the other way round - switch monitoring off and lvmetad afterwards. --- scripts/lvm2_monitoring_systemd_red_hat.service.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/lvm2_monitoring_systemd_red_hat.service.in b/scripts/lvm2_monitoring_systemd_red_hat.service.in index a8d51838..425cb0d3 100644 --- a/scripts/lvm2_monitoring_systemd_red_hat.service.in +++ b/scripts/lvm2_monitoring_systemd_red_hat.service.in @@ -2,7 +2,7 @@ Description=Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling Documentation=man:dmeventd(8) man:lvcreate(8) man:lvchange(8) man:vgchange(8) Requires=dm-event.socket -After=dm-event.socket fedora-storage-init.service fedora-storage-init-late.service +After=dm-event.socket fedora-storage-init.service fedora-storage-init-late.service lvm2-lvmetad.service Before=local-fs.target DefaultDependencies=no Conflicts=shutdown.target -- cgit