Slow initialization of something during boot

[Gregory Hosler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/14/2013 12:49 AM, Frank wrote:
> Since I made the switch to a 64 bit machine (still using 32 bit Fedora 19)
> there is a long delay just before lightdm comes up with the login screen. 
> Can someone take a look at this output and perhaps point out why and where
> it's occurring ? By the way I don't use LVM or raid...can I disable these
> services? What;s the best way to do that. Even so the time they take 
> doesn't account for the 6-7 second delay after booting before lightdm comes
> up.
> 
> Thanks for any help
> 
> 
> [frank at localhost ~]$ sudo systemd-analyze blame 19.698s
> NetworkManager.service 19.597s accounts-daemon.service 18.723s
> chronyd.service 18.567s lightdm.service 2.406s lvm2-monitor.service

NOTE: the time stamp is as the start of the service, not at the end.

so, right here. LVM startup

16 secs for lvm startup is nothing. :-)

How many VG and LV you have ?

I have 32 lv's spread across 3 VG's and 5 GB spread across 3 PV's (one for
each VG).

It takes me between 2 to 3 minutes (about 150 to 180 secs) to do the lvm
initialization.

What I have found to help was to do the LV initialization as part of the
initial boot stage.

On my kernel boot line in grub.conf, I have the following:

	rd.lvm.vg=INSTALLATION rd.lvm.vg=VM rd.lvm.vg=ClassRoom
	rd.lvm.lv=INSTALLATION/F19

The rd.lvm.vg's are my multiple (3) VG's
The rd.lvm.lv is the /

There will STILL be a delay. In my case, the delay is about 3 minutes (as I
noted above). w/o the rd.lvm.vg it would take noticeably longer.

Hope that helps, your mileage may vary.

All the best,

- -Greg

> 2.317s dmraid-activation.service 1.487s systemd-udev-settle.service 1.467s
> systemd-tmpfiles-setup-dev.service 1.152s fedora-loadmodules.service 1.074s
> systemd-fsck-root.service 706ms polkit.service 656ms
> systemd-sysctl.service 581ms fedora-readonly.service 537ms
> systemd-logind.service 510ms sys-kernel-debug.mount 508ms dev-mqueue.mount 
> 508ms rtkit-daemon.service 505ms dev-hugepages.mount 500ms
> media-debian.mount 485ms tmp.mount 353ms systemd-udev-trigger.service 294ms
> plymouth-start.service 265ms systemd-readahead-replay.service 243ms
> lvm2-lvmetad.service 216ms systemd-random-seed-load.service 165ms
> sys-kernel-config.mount 156ms systemd-readahead-collect.service 152ms
> systemd-remount-fs.service 138ms systemd-tmpfiles-setup.service 89ms
> plymouth-read-write.service 88ms plymouth-quit.service 86ms
> plymouth-quit-wait.service 70ms systemd-udevd.service 34ms
> systemd-user-sessions.service 32ms livesys.service 27ms
> home-frank-external.mount 25ms livesys-late.service 21ms
> systemd-vconsole-setup.service 13ms auditd.service 10ms
> systemd-journal-flush.service 3ms rpcbind.service 3ms
> systemd-update-utmp-runlevel.service 1ms systemd-readahead-done.service


- -- 
+---------------------------------------------------------------------+

Please also check the log file at "/dev/null" for additional information.
                (from /var/log/Xorg.setup.log)

| Greg Hosler                                   ghosler at redhat.com    |
+---------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlIK9v0ACgkQ404fl/0CV/QwJgCg4TntRJSFz/G/irI7F0HjVf1O
u5MAoKmc0DwM7Vw5XLbvKjOdYvEpxwKc
=btkw
-----END PGP SIGNATURE-----