Bug#791869: lvm2: updating src:lvm2 from 2.02.111-2.2 to 2.02.122-1 breaks booting, mounting LVs other than / fails

Peter Rajnoha prajnoha at redhat.com
Mon Jul 27 14:27:17 UTC 2015

On 07/27/2015 04:12 PM, Peter Rajnoha wrote:
> It's the OPTIONS+="db_persist" that needs to be used in initramfs
> for MD devices. This marks udev db records related to this device with
> sticky bit then which is then recognized by udev code and the udev
> db state is not cleaned up in that case:

For example, dracut (the initramfs environment used also in RH systems)
has these rules to handle MD devices (it has the OPTIONS+="db_persist"):


If you already use this in Debian and it doesn't work, it must be
a regression in some version of udev as I've already gone through
this with Harald Hoyer and Kay Sievers who take care of udev.

Simply, this is the correct sequence that should be used:

 - udev running in initramfs
 - mark records with OPTIONS+="db_persist" for devices that require that
   (currently it's the MD and DM)
 - udev in initramfs stopped
 - udev database copied from initramfs to root fs

--- switch to root fs ---

 - udev running in root fs
 - udevadm info --cleanup-db (but will keep the records marked from
initramfs with the db_persist flag)
 - udevadm trigger --action=add for the coldplug


More information about the pkg-lvm-maintainers mailing list