http://bugzilla.suse.com/show_bug.cgi?id=1014757
http://bugzilla.suse.com/show_bug.cgi?id=1014757#c2
--- Comment #2 from Mikhail Kasimov
Hi,
Sorry for the delay...
No problem at all. :)
(In reply to Mikhail Kasimov from comment #0)
Can you see -.mount here? I can't. :)
I think it's a current limitation: systemd assumes the *current* root fs to be setup when PID1 was started (otherwise systemd couldn't have been executed at all). So it has no idea how long the previous mount operation took therefore "-.mount" is not displayed by "systemd-analyze blame".
However you can still find out the information you're looking for: the final root fs is mounted by the initramfs on /sysroot directory. For some reasons the unit used to mount /sysroot is still present in the host system:
$ systemd-analyze blame | grep sysroot.mount 181ms sysroot.mount
My current output: ======================== k_mikhail@linux-mk500:~> systemd-analyze blame | grep sysroot.mount k_mikhail@linux-mk500:~> ========================
I must admit I don't know why this unit is still kept around as it shouldn't be needed since PID1 switched to the new rootfs.
Anyways if you feel this should be improved, please discuss this with upstream.
No, thanks! -- You are receiving this mail because: You are on the CC list for the bug.