[systemd-devel] encrypted /var with systemd - impossible?

[yoshi watanabe]

my guess is that systemd populates /var before mounting it, and then
mounts it over and some files are possibly lost. or maybe because the
/var is empty before mount and that causes problems.

i'll run a debug boot in a minute and post results.

2011/6/27 Lennart Poettering <lennart at poettering.net>:
> On Mon, 27.06.11 14:49, yoshi watanabe (yoshi314 at gmail.com) wrote:
>
>> Hi list (again) ;)
>>
>> In short : my setup is as follows - i have my / on ssd, so i decided
>> to move /var over to regular hdd. which is entirely encrypted (lvm
>> inside luks, /var is one of lvm volumes).
>>
>> This works just fine on various distributions i tried
>> (gentoo,arch,exherbo,probably opensuse as well), usually with dracut
>> as initrd system and their default init systems.
>>
>> when using systemd, regardless of underlying distribution, system does
>> not boot correctly. it usually locks up somewhere during boot, waiting
>> for something.
>>
>> i tried it with clean default fedora 15 install (just set up /var as
>> encrypted lvm partition), i also tried it with exherbo and with
>> gentoo. they all either get stuck, or boot up into half-working
>> environment.
>>
>> i suppose that kind of setup appears to be totally
>> systemd-incompatible. or is it a bug?
>
> This is a bug.
>
> Please boot with "systemd.log_level=debug systemd.log_target=kmsg" and
> disable all graphical boot splashes. Then boot, wait until it locks up,
> wait a bit more, then post the last generated output from screen.
>
> Lennart
>
> --
> Lennart Poettering - Red Hat, Inc.
>