On Wednesday 22 June 2016 12:10:14 Dennis Semakin wrote:
> The task is to obtain messages _only_ with specified fields (e.g.
> MESSAGE_ID=bla-bla-bla).
> And problem is that I can see incoming messages even when sending tool is
> not running (no execution). Looks like I got all messages from jour
Thanks for your answer. Turns out this problem is not really about LVM.
I've described the more general problem here:
https://bugs.freedesktop.org/show_bug.cgi?id=85746
I don't know if that's expected or not, but I'd like to have some clearings
if I'm doing something that I shouldn't do or not.
A
Sorry for the spam. Further tracking down the issue. I think I've come to a
conclusion of the scenario:
S1.service requires/after D.device and S2.service
S1 is activating, thus starts D and S2
S2 starts, which activates D and deactivates D
A "can" now start because D has no job running [1], but D
I've tracked down the issue a little.
sysroot.mount requires/after dev-vg-lv.device.
System start, dev-vg-lv is inactive.
vgchange -a y -> dev-vg-lv active.
vgchange -a n -> dev-vg-lv inactive.
At this point, unit->job of dev-vg-lv is NULL (sometimes also happens when
I don't run vgchange, but I
Hi, I'm going on with my work to have systemd in initrd on NixOS (using
dracut is a little complicated at the moment).
Everything works fine, I've ported luks and lvm and both work separately.
However I'm hitting a problem when using luks and lvm on top of luks.
SETUP
Software: systemd 212, lvm 2
>
>
> As you already mentioned, you'd have to make sure you manage to pass
> through the state correctly.
>
>
Thanks. Is there any docs I can read about this or just read the code? It
appears that systemd dumps the state into a file, and afterwards it's
passed to the new systemd instance.
_
Thank you all for the replies. After the first answers I've ported the
initrd to systemd (only the basic stuff, no luks, lvm, etc.) and works very
fine.
Except one thing, that I hoped to find in dracut but does not seem to do
anything special about it. It just goes through switch-root it seems.
As
I'm going to do an experiment with NixOS: replace the whole current initrd
process made of scripts and hooks with systemd.
Before doing any work however I'd like to hear whether systemd in initrd is
still wanted in the future, or there's any possible idea about dropping
this support.
Also, apart