08.01.2015 3:43, Lennart Poettering: [...]
The fsck of the root file system is done by systemd-root-fsck.service. It exists both in the initrd and on the host.
On my box the first check is performed by systemd-fsck@ (I can see it in the log), and the second by systemd-root-fsck apparently.
When the transition between the initrd and the host takes place
the state of the unit is serialized/unserialized. And since RemainAfterExit=yes is set if it was started once it will not be started again because it will still be considered started. Maybe suse forgot to include this service file in the initrd or so?
Indeed, systemd-root-fsck.service is not present in initrd here (although systemd-fsck@.service is).
So probably it is either suse's fault or dracut's fault. Thank you, Nikolai
Lennart
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
