Felix Miata wrote:
Those too failed to have any discernible effect. LVM timestamp where delay occurred has dropped from 13.# previously to 9.#.
14.565s systemd-fsck@dev-disk-by\x2dlabel-fedora20.service 12.213s systemd-fsck@dev-disk-by\x2dlabel-15pub.service 11.502s systemd-fsck@dev-disk-by\x2dlabel-os131p20.service 10.788s systemd-fsck@dev-disk-by\x2dlabel-suse122.service 10.349s systemd-fsck@dev-disk-by\x2dlabel-14usrlcl.service 9.008s systemd-fsck@dev-disk-by\x2dlabel-suse123.service 8.515s systemd-fsck@dev-disk-by\x2dlabel-suse121.service 6.781s systemd-fsck@dev-disk-by\x2dlabel-fedora19.service 6.206s systemd-fsck@dev-disk-by\x2dlabel-13home.service 4.811s disks-E.mount 4.522s systemd-fsck@dev-disk-by\x2dlabel-03boot.service 4.041s network.service 3.441s systemd-fsck@dev-disk-by\x2dlabel-fedora18.service 2.937s systemd-fsck-root.service 2.505s disks-C.mount 2.467s rpcbind.service 2.438s systemd-udev-root-symlink.service 2.327s systemd-fsck@dev-disk-by\x2dlabel-suse114.service
---- Is that a breakdown and your system booted in 14.5s or is that cumulative @ 2 minutes? cf. /etc/sysVinit on a large system with 40+TB of disk space: 38 seconds to login prompt from when kernel starts boot (services start ~12 seconds, all FS's mounted at 19.2s... remainder of time is service starts... ----------- If that's a breakdown, you have sysVinit by a good 24 seconds! If it is cumulative, um... that wouldn't be good. If fsck is your prob, tried XFS? (no fsck... file system mounts start at 15.8s and finish at 19.2 for ~16 file file systems w/10 on device mapper). I really hope that is a breakdown, since systemd was supposed to be so much faster than sysVinit...those figures don't make sense... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org