On Tue, Nov 5, 2019 at 12:04 PM Mike Snitzer <snitzer@xxxxxxxxxx> wrote: > On Mon, Nov 04 2019 at 10:43am -0500, > David Michael <fedora.dm0@xxxxxxxxx> wrote: > > > Hi, > > > > I would like to be able to use a root device configured by > > dm-mod.create with an initrd in some scenarios, but it appears that > > the default udev rules do not recognize this setup which prevents > > systemd from mounting the root file system. There is a systemd bug > > report with a demo script to illustrate what I mean.[1] Has anyone > > here encountered this, or is there a solution already? > > Why do you want this? dm-mod.create and initrd are mutually > exclussive... that was/is the point. I am using the same image building process for custom systems with dm-init etc. built into the kernel and for Fedora-based systems, which require an initrd to load the device mapper kernel modules as well as NVMe support so it can find the devices in the first place. I'd prefer to be uniform and use dm-mod.create everywhere rather than bundle the configuration into an initrd for certain distros (or be uniform by creating initrds for my custom builds that don't otherwise need one). As mentioned in the systemd bug, dm-mod.create works correctly with an initrd aside from udev needing to be manually triggered before systemd can use it. I was looking for suggestions for how this could be handled upstream ideally so I don't have to customize an initrd to add a udevadm trigger. Thanks. David -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
