Control: reassign -1 lvm2 On Thu, Apr 18, 2024 at 02:24:06PM +0500, Alex Volkov wrote: > On четверг, 18 апреля 2024 г. 11:38:18 +05 Mark Hindley wrote: > > > udevadm: info --cleanup-db > > "db_persist=" -> "db_persist" > > require explicit "db_persist" to exclude device info from --db-cleanup > > Wow. I knew there's something in this transition to --db-cleanup. > > > Does this mean that dm mapper should set db_persist in the initramfs? > > More like it's actually needs to be set by the corresponding udev rule in lvm2 > package (which does all that device-mapper devices detection). I tried adding > the corresponding OPTIONS+="db_persist" line into 55-dm.rules file and it > worked as intended. I will report the bug to lvm2.
I think we can just reassign this one. Dear lvm2 maintainers, We have been investigating why devices discovered by the initramfs were being cleaned by /etc/init.d/udev. The udev initscript runs udevadm info --cleanup-db. It appears to be the responsibility of devices that should not be cleaned to set db_persist in their setup rule. There appears to be a recent upstream lvm2 commit to address this[1]. Thanks Mark [1] https://gitlab.com/lvmteam/lvm2/-/commit/eb4f744820832aff3d6da1bba14f12e91a5b3535
