On Sun, 29.03.15 20:42, Dominik Brodowski (li...@dominikbrodowski.net) wrote:
> Dear systemd developers, > > In my custom initramfs, lvm vgmknodes successfully creates the device > nodes for /dev/vg0/home and /dev/vg0/swap . On current sytemd/udev systems device nodes are created via devtmpfs by the kernel, userspace does not create them. A command like "lvm vgmknodes" creates device nodes, right? It is hence obsolete. In general, please direct LVM questions to the LVM project, it's not our area of expertise. > However, /home is left unmounted > and swap is still off. Then, after handing business over to systemd (with > /dev re-mounted), and after some services are activated successfully, > systemd enters an emergency shell: The (autogenerated) > systemd-cryptsetup@home.service and systemd-cryptsetup@swap.service want > dev-vg0-home.device and dev-vg0-swap.device to be ready, but > > $ systemctl status dev-vg0-home.device > and $ systemctl status dev-vg0-swap.device > > show they are inactive -- even though the device nodes at /dev/vg0/home and > /dev/vg0/swap actually exists and are working! Well, if you create device nodes on your own, without involvement of the kernel, and without them being announced via the kernel/udev, then systemd will not know about them. Either way, I figure you need to ask Debian downstream and LVM for help about this. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
