Am 09.03.2014 18:39, schrieb Canek Peláez Valdés:
Something is wrong here; unless you are booting a 386 machine, there
is no way it should take a minute and a half to boot. And even with a
386 I would be suspicious.
No, actually it is an Intel i5-4670K with 8 GB of RAM.
Something is seriously wrong with systemd-tmpfiles-clean.service; why
it takes 1:07 minutes to run? Do you have /tmp as a tmpfs?
Yes, at least according to mount, it is.
mount | grep tmpfs
devtmpfs on /dev type devtmpfs
(rw,relatime,size=238864k,nr_inodes=59716,mode=755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
tmpfs on /tmp type tmpfs (rw)
By the way my actual blame does tell:
systemd-analyze blame
6.087s NetworkManager.service
5.310s alsa-restore.service
4.226s systemd-logind.service
3.660s lightdm.service
2.581s systemd-vconsole-setup.service
688ms polkit.service
479ms systemd-user-sessions.service
413ms kmod-static-nodes.service
381ms systemd-udev-trigger.service
358ms user@0.service
352ms systemd-tmpfiles-setup-dev.service
274ms tmp.mount
265ms systemd-journal-flush.service
246ms systemd-sysctl.service
235ms systemd-random-seed.service
205ms upower.service
205ms udisks2.service
197ms systemd-udevd.service
195ms systemd-tmpfiles-setup.service
183ms systemd-fsck-root.service
163ms systemd-remount-fs.service
126ms systemd-update-utmp.service
125ms sys-fs-fuse-connections.mount
53ms wpa_supplicant.service
50ms user@1000.service
50ms accounts-daemon.service
Actual systemd-analyze:
Startup finished in 584542y 2w 2d 20h 1min 42.032s (loader) + 1.540s
(kernel) + 11.028s (userspace) = 12.569s
Actual critical chain:
graphical.target @11.028s
└─multi-user.target @11.028s
└─NetworkManager.service @4.940s +6.087s
└─basic.target @4.939s
└─timers.target @4.721s
└─systemd-tmpfiles-clean.timer @4.721s
└─sysinit.target @4.489s
└─systemd-vconsole-setup.service @1.907s +2.581s
└─systemd-journald.socket @1.660s
└─-.mount @1.660s
└─system.slice @2.030s
└─-.slice @2.030s
Could you run "systemd-analyze critical-chain systemd-tmpfiles-clean.service"?
Sure, here it is:
└─systemd-tmpfiles-clean.timer @4.721s
└─sysinit.target @4.489s
└─systemd-vconsole-setup.service @1.907s +2.581s
└─systemd-journald.socket @1.660s
└─-.mount @1.660s
└─system.slice @2.030s
└─-.slice @2.030s
In your critical-chain systemd-tmpfiles-clean.service was not included
(only systemd-tmpfiles-clean.timer). From blame, I think that's the
obvious offender. Again, do you have /tmp as a tmpfs? What do you have
in /etc/tmpfiles.d?
/etc/tmpfiles.d is empty.
Notice that systemd-tmpfiles-clean.service takes almost no time; here
it's its critical chain:
Yes, I see, so makes me wonder.
BTW, my fstab:
/dev/sda1 /boot ext2 noauto,noatime 0 0
/dev/sda2 / xfs noatime,nodiratime 0 0
Thanks.
