Bug 712539

Created attachment 446065 [details]
Patch to move dmeventd start after local filesystem mounting

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0

If root is on a LVM LV, we get a number of error messages on boot
about "failure to start dmeventd", "event registration failed" etc.
This is due to dmeventd now being part of device-mapper and 
automatically started to monitor eg. RAID-1 style devices with the 
"mirror" plugin.

However, dmeventd is a.) not part of the initrd and b.) requires /var
and possibly other resources. Generally, it does not make sense to
enable monitoring until all local filesystems have available. vgchange
got a --sysinit parameter added because of this.

This patch:
- adds "--sysinit" to the initrd boot-lvm2.sh script responsible of
  making LVM VGs available (not even a root filesystem available at 
  this stage)
- adds "--sysinit" to the full-blown boot.lvm start script (if eg. 
  /var is on LVM, vgchange will yield errors here, too)
- adds a new /etc/init.d/boot.lvm_monitor script that enables 
  monitoring just after local filesystems have become available

This is the same behaviour that eg. Arch Linux and Gentoo have 
adopted (Credits to them for the idea behind the fix).

See eg. https://bugs.archlinux.org/task/18153

Reproducible: Always

Steps to Reproduce:
1. Install with / (root) and/or /var on a LV
2. Boot
Actual Results:  
Error messages "Unable to start dmeventd", "event registration failed"
More important: dmeventd not working!

Expected Results:  
Start dmeventd when local filesystems are available