Bug#727708: systemd status when using multiple block device layers (MD/LVM/dm-crypt) below the root-fs
Hi.
Now that systemd could become default in Debian (well at least I favour
it over upstream)... I started wondering how well it supports booting
from a root fs on top of multiple block device layers?
Some time ago I wrote [0] (with some contributions from others
AFAICS)...
So is there any information from the side of the systemd (Debian)
maintainers, how far these scenarios are supported already?
Right now there is a rather fixed order in which things work (i.e.
phys->MD->LVM->dm-crypt->rootfs) out of the box (well in some cases at
least) and IIRC, due to some "obscure" code in the cryptsetup initramfs
scripts it works also with (dm-crypt->LVM)... but ideally all this
should be handled more generally...
Looking over the bugs from the systemd package in Debian give quite some
concern here,... many things seem to not work yet (e.g. support for
cryptsetup key scripts)... and many other bugs seem to be quite old and
not having been worked on for very long.
There's also the issue that apparently there are subtle issues when it
comes to udev rules deployed with systemd or that systemd needs in a
specific way (e.g. #712439) ... where we have problems since Debian
maintainers from other packages divert from the upstrem udev rules for
whichever reason.
Cheers,
Chris.
[0] https://wiki.debian.org/AdvancedStartupShutdownWithMultilayeredBlockDevices
Reply to: