http://bugzilla.suse.com/show_bug.cgi?id=936363 http://bugzilla.suse.com/show_bug.cgi?id=936363#c16 --- Comment #16 from Mike Galbraith <mgalbraith@suse.com> --- (In reply to Thomas Blume from comment #12)
systemd-fstab-generator is still present in the initrd. It is only moved out of the generator directory in order to avoid a race with dracut-rootfs-generator. When dracut-rootfs-generator successfully finishes, systemd-fstab-generator is moved back to do the remount. I could add a condition that moves it back instead of running dracut-rootfs-generator when the kdump initrd is used.
Hm. Dunno if it's useful, but whacking first hunk (below) "fixes" it. Index: dracut-037/modules.d/98systemd/module-setup.sh =================================================================== --- dracut-037.orig/modules.d/98systemd/module-setup.sh 2015-05-11 18:17:47.824360623 +0200 +++ dracut-037/modules.d/98systemd/module-setup.sh 2015-05-11 18:17:49.952480263 +0200 @@ -43,7 +43,6 @@ $systemdutildir/systemd-sysctl \ $systemdutildir/systemd-modules-load \ $systemdutildir/systemd-vconsole-setup \ - $systemdutildir/system-generators/systemd-fstab-generator \ $systemdutildir/system-generators/systemd-gpt-auto-generator \ \ $systemdsystemunitdir/cryptsetup.target \ -- You are receiving this mail because: You are on the CC list for the bug.