I hit this problem on a server here where I have / on lvm2, and it failed to boot since lvm was not added to initrd ;/ (dracut lvm module depends on dracut dm module that depends on dmsetup being available) Advisory: Updated lvm2 packages adds missing dependency On a system that uses lvm2 we need to ensure that dmsetup is installed. Without it lvm2 wont get added to initrd, causing the system to fail to boot if root is on lvm. This update adds the dependency on dmsetup, ensuring the system boots as intended. SRPMS: lvm2-2.02.183-1.1.mga7.src.rpm i586: dmsetup-1.02.154-1.1.mga7.i586.rpm libdevmapper1.02-1.02.154-1.1.mga7.i586.rpm libdevmapper-devel-1.02.154-1.1.mga7.i586.rpm libdevmapper-event1.02-1.02.154-1.1.mga7.i586.rpm libdevmapper-event-devel-1.02.154-1.1.mga7.i586.rpm liblvm2app2.2-2.02.183-1.1.mga7.i586.rpm liblvm2cmd2.02-2.02.183-1.1.mga7.i586.rpm liblvm2cmd-devel-2.02.183-1.1.mga7.i586.rpm liblvm2-devel-2.02.183-1.1.mga7.i586.rpm lvm2-2.02.183-1.1.mga7.i586.rpm x86_64: dmsetup-1.02.154-1.1.mga7.x86_64.rpm lib64devmapper1.02-1.02.154-1.1.mga7.x86_64.rpm lib64devmapper-devel-1.02.154-1.1.mga7.x86_64.rpm lib64devmapper-event1.02-1.02.154-1.1.mga7.x86_64.rpm lib64devmapper-event-devel-1.02.154-1.1.mga7.x86_64.rpm lib64lvm2app2.2-2.02.183-1.1.mga7.x86_64.rpm lib64lvm2cmd2.02-2.02.183-1.1.mga7.x86_64.rpm lib64lvm2cmd-devel-2.02.183-1.1.mga7.x86_64.rpm lib64lvm2-devel-2.02.183-1.1.mga7.x86_64.rpm lvm2-2.02.183-1.1.mga7.x86_64.rpm For testers, simply install lvm2 from release (and check that you dont have dmsetup installed), then install lvm2 from testing and it should pull in dmsetup
Have just checked the status of these packages and find that both lvm2 and dmsetup are installed. $ rpm -qa | grep lvm2 lib64lvm2app2.2-2.02.183-1.mga7 lib64lvm2cmd2.02-2.02.183-1.mga7 lvm2-2.02.183-1.mga7 $ rpm -qa | grep dmsetup dmsetup-1.02.154-1.mga7 An attempt at removing dmsetup offered to remove most of my Mate installation as well so that is a no-go. Is there any way to get rid of dmsetup just by itself?
CC: (none) => tarazed25
Ah, yeah it seems almost every DE has deps that to pull it in, so this is more an issue on clean server installs... You can remove a package with: rpm -e --nodeps <package_name> so in this case: rpm -e --nodeps dmsetup
Thanks Thomas - what a newbie - I was using urpmi --nodeps.
$ rpm -qa | egrep "dmsetup|lvm2" lib64lvm2app2.2-2.02.183-1.mga7 lib64lvm2cmd2.02-2.02.183-1.mga7 lvm2-2.02.183-1.mga7 # urpmi lvm2 To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Updates Testing") dmsetup 1.02.154 1.1.mga7 x86_64 lib64devmapper-event1.02 1.02.154 1.1.mga7 x86_64 lib64lvm2cmd2.02 2.02.183 1.1.mga7 x86_64 lvm2 2.02.183 1.1.mga7 x86_64 That worked fine. OK for 64 bits.
Whiteboard: (none) => MGA7-64-OK
Same test done for i586. Ok for 32 bits.
CC: (none) => lists.jjorgeWhiteboard: MGA7-64-OK => MGA7-64-OK MGA7-32-OK
Created attachment 11162 [details] CLI - online cloning partition with lvm and snapshots Cloned a LVM partition with lvm commands and snapshotting. Everything ok. Arch is x86_64. Ulrich
CC: (none) => bequimao.de
Advisory uploaded, validating.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0056.html
Status: NEW => RESOLVEDResolution: (none) => FIXED