Hi,
On 14-11-15 14:09, Michael Biebl wrote:
And alternative could be, to attach the output of systemd-analyze and
"systemd-analyze blame" when such a long fsck happens.
I thought I had already done that, but here it is again in full.
$ systemd-analyze
Startup finished in 3.802s (kernel) + 9min 50.031s (userspace) = 9min
53.833s
and blame:
9min 32.488s systemd-fsck@dev-sda1.service
9min 31.695s systemd-fsck@dev-sda6.service
16.290s rc-local.service
1.528s apache2.service
1.065s nmbd.service
1.024s samba-ad-dc.service
649ms shorewall.service
544ms media-olddisk6.mount
331ms dev-sdg1.device
325ms ModemManager.service
271ms systemd-localed.service
252ms NetworkManager.service
201ms systemd-hostnamed.service
175ms smbd.service
171ms accounts-daemon.service
168ms home-manuel-photos.mount
149ms home-manuel-Documents.mount
116ms systemd-timesyncd.service
116ms home-manuel-Pictures.mount
109ms udisks2.service
107ms systemd-modules-load.service
98ms exim4.service
81ms iio-sensor-proxy.service
80ms console-setup.service
79ms keyboard-setup.service
68ms systemd-udevd.service
65ms polkitd.service
65ms rsyslog.service
64ms timidity.service
62ms alsa-restore.service
55ms minissdpd.service
53ms systemd-udev-trigger.service
47ms home-manuel-Music.mount
39ms networking.service
38ms wpa_supplicant.service
36ms home-manuel-Videos.mount
35ms systemd-journald.service
35ms packagekit.service
33ms irqbalance.service
31ms systemd-logind.service
30ms avahi-daemon.service
29ms systemd-tmpfiles-setup-dev.service
27ms media-olddisk1.mount
25ms user@1000.service
23ms kbd.service
21ms systemd-setup-dgram-qlen.service
21ms home-manuel-msx\x2dsoft.mount
20ms user@116.service
20ms speech-dispatcher.service
16ms pppd-dns.service
15ms systemd-user-sessions.service
15ms dev-hugepages.mount
15ms dev-mqueue.mount
14ms gdomap.service
13ms sys-kernel-debug.mount
12ms gdm.service
12ms upower.service
10ms systemd-tmpfiles-setup.service
10ms colord.service
9ms
dev-disk-by\x2duuid-0a3f3e1b\x2d1141\x2d4033\x2db619\x2dec2f6d6
5ms rtkit-daemon.service
5ms systemd-random-seed.service
5ms systemd-journal-flush.service
5ms systemd-update-utmp.service
4ms home-manuel-docs.mount
4ms systemd-tmpfiles-clean.service
4ms kmod-static-nodes.service
4ms systemd-remount-fs.service
3ms systemd-sysctl.service
3ms systemd-update-utmp-runlevel.service
See my first bug report where I already included the top of the blame
output.
My conclusion was that it was in systemd, so that's why I filed to bug
against systemd. But I might be wrong :) Your opinion, please! :)
--
Kind regards,
Manuel
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
