Bug#754078: crypt devices not brought online (backed by iscsi)

[Lennart Poettering]

On Sun, 20.07.14 15:58, Michael Biebl (biebl at debian.org) wrote:

> > Currently, with systemd, it gets to where it'd like to bring up the
> > crypt devices. As network and open-iscsi aren't up yet, it wastes a lot
> > of time waiting for block devices that will never appear (at least not
> > without further action later in the boot process).
> 
> Hm, k. So I guess we'd need something like a cryptsetup-pre.target,
> where certain units can hook into (via Wants/Before), network.target
> being one of them.
> And devices flagged noearly would get a dependency on this target and be
> ordered after it.
> 
> Lennart, do you have a different/better idea how we could handle such
> setups which have more complex requirements, like cryptsetup devices
> being backed by iscsi which in turn requires network access?

Not following here. In contrast to classic sysv the jobs actually stay
queued until the devices show up. If you have iscsi devices that shall
be mounted during boot, then you really need to make sure that iscsi can
work in early boot. Then, if iscsi needs the network, then your network
system needs to be able to run in early-boot too.

I have the suspcicion this works on Fedora already.

But generally, the old Debian scheme of running cryptsetup twice doesn't
really apply to systemd, since we never scan for devices, we just
subscribe to them.

Anyway, still not grokking the actual problem here I must say...

Lennart

-- 
Lennart Poettering, Red Hat