[systemd-devel] systemd 204 to 215 (Debian version) fails to recognize that LVM2 device nodes are already present and accessible

[Dominik Brodowski]

Dear systemd developers,

In my custom initramfs, lvm vgmknodes successfully creates the device
nodes for /dev/vg0/home and /dev/vg0/swap . 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 at home.service and systemd-cryptsetup at 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!

A workaround for this bug is to mask these devices:

	$ systemctl mask /etc/systemd/system/dev-vg0-home.device
	$ systemctl mask /etc/systemd/system/dev-vg0-var.device

Is there any better option available?

Many thanks for taking a look at this issue.

Best,
	Dominik

[*] Debian version 215-12. The issue is present (at least) since 204-8, see
Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745390 . I
_could_ try out upstream systemd if really needed, but maybe that's not
necessary?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150329/6b463be0/attachment.sig>