| Summary: | dbraid service takes an extraordinary amount of time during boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | mikey <abc.mikey> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | johannbg, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-08 19:25:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Booting with dmraid-acitvation.service disabled:
2.216s plymouth-quit-wait.service
2.014s firewalld.service
1.735s abrtd.service
1.666s var.mount
1.651s usr-local.mount
1.301s libvirtd.service
1.218s accounts-daemon.service
869ms systemd-fsck@dev-disk-by\x2duuid-fb45532d\x2dc071\x2d4612\x2d96d3\x2de7a6066a4982.service
559ms plymouth-start.service
506ms polkit.service
485ms upower.service
473ms dev-sdb5.device
293ms systemd-journal-flush.service
285ms gssproxy.service
262ms packagekit.service
156ms mnt-store.mount
155ms lm_sensors.service
149ms fedora-import-state.service
143ms bluetooth.service
143ms udisks2.service
141ms user
136ms avahi-daemon.service
134ms proc-fs-nfsd.mount
133ms user
133ms iio-sensor-proxy.service
117ms plymouth-read-write.service
105ms systemd-udevd.service
95ms chronyd.service
92ms NetworkManager.service
88ms systemd-udev-trigger.service
83ms systemd-fsck@dev-disk-by\x2duuid-d62912c7\x2d95f0\x2d44e8\x2d9504\x2d3c9d3c901f8e.service
82ms systemd-tmpfiles-setup-dev.service
76ms systemd-vconsole-setup.service
69ms systemd-fsck@dev-disk-by\x2duuid-b1787794\x2d5a3e\x2d4801\x2d87be\x2dde1d5264deef.service
66ms systemd-fsck@dev-disk-by\x2duuid-5d4252a5\x2d5398\x2d4a3b\x2db465\x2d8eae5f6a23d1.service
65ms systemd-logind.service
65ms gdm.service
63ms dev-disk-by\x2duuid-d3d178c6\x2d9932\x2d4c8f\x2d9deb\x2de266b22a1267.swap
61ms fedora-readonly.service
61ms auditd.service
59ms systemd-binfmt.service
58ms systemd-tmpfiles-setup.service
55ms boot.mount
55ms systemd-localed.service
51ms home.mount
50ms systemd-journald.service
50ms abrt-ccpp.service
47ms wpa_supplicant.service
44ms cups.service
43ms kmod-static-nodes.service
42ms systemd-sysctl.service
38ms proc-sys-fs-binfmt_misc.mount
37ms colord.service
36ms rtkit-daemon.service
36ms systemd-remount-fs.service
34ms dev-hugepages.mount
33ms rpc-statd-notify.service
33ms nfs-config.service
31ms tmp.mount
31ms netcf-transaction.service
30ms dev-mqueue.mount
27ms dracut-shutdown.service
25ms systemd-random-seed.service
24ms systemd-fsck@dev-disk-by\x2duuid-d9710dda\x2da514\x2d4c5f\x2d9c5a\x2d6056e74937c7.service
20ms systemd-rfkill.service
16ms systemd-fsck-root.service
13ms blk-availability.service
13ms systemd-user-sessions.service
11ms sys-kernel-debug.mount
10ms sys-fs-fuse-connections.mount
8ms systemd-update-utmp.service
7ms var-lib-nfs-rpc_pipefs.mount
4ms systemd-update-utmp-runlevel.service
1ms sys-kernel-config.mount
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: Boot times as shown: 49.864s dmraid-activation.service 2.866s plymouth-quit-wait.service 1.298s firewalld.service 996ms abrtd.service 846ms systemd-journal-flush.service 840ms libvirtd.service 664ms plymouth-start.service 555ms var.mount 550ms usr-local.mount 540ms boot.mount 537ms upower.service 489ms accounts-daemon.service 416ms lm_sensors.service 392ms dev-sdb5.device 370ms gssproxy.service 250ms packagekit.service 238ms chronyd.service 235ms systemd-logind.service 192ms avahi-daemon.service 166ms mnt-store.mount 162ms rtkit-daemon.service 160ms bluetooth.service 160ms udisks2.service 155ms proc-fs-nfsd.mount 160ms udisks2.service 155ms proc-fs-nfsd.mount 140ms user 136ms user 117ms fedora-import-state.service 108ms cups.service 100ms polkit.service 97ms plymouth-read-write.service 97ms systemd-udevd.service 92ms systemd-fsck@dev-disk-by\x2duuid-fb45532d\x2dc071\x2d4612\x2d96 84ms NetworkManager.service 79ms systemd-vconsole-setup.service 76ms systemd-udev-trigger.service 67ms systemd-journald.service 66ms gdm.service 63ms systemd-tmpfiles-setup-dev.service 61ms dev-hugepages.mount 61ms systemd-remount-fs.service 61ms dev-mqueue.mount 59ms sys-kernel-debug.mount 56ms dev-disk-by\x2duuid-d3d178c6\x2d9932\x2d4c8f\x2d9deb\x2de266b22 53ms auditd.service 52ms systemd-binfmt.service 52ms systemd-tmpfiles-setup.service 49ms systemd-sysctl.service 48ms systemd-fsck@dev-disk-by\x2duuid-5d4252a5\x2d5398\x2d4a3b\x2db4 47ms systemd-fsck@dev-disk-by\x2duuid-d62912c7\x2d95f0\x2d44e8\x2d95 47ms tmp.mount 43ms abrt-ccpp.service 39ms fedora-readonly.service 35ms home.mount 34ms rpc-statd-notify.service 32ms systemd-fsck@dev-disk-by\x2duuid-b1787794\x2d5a3e\x2d4801\x2d87 30ms proc-sys-fs-binfmt_misc.mount 27ms colord.service 26ms wpa_supplicant.service 25ms netcf-transaction.service 24ms systemd-fsck@dev-disk-by\x2duuid-d9710dda\x2da514\x2d4c5f\x2d9c 20ms iio-sensor-proxy.service 20ms nfs-config.service 16ms systemd-fsck-root.service 16ms systemd-rfkill.service 14ms systemd-user-sessions.service 12ms dracut-shutdown.service 11ms blk-availability.service 11ms kmod-static-nodes.service 10ms systemd-random-seed.service 9ms systemd-update-utmp.service 9ms var-lib-nfs-rpc_pipefs.mount 7ms systemd-update-utmp-runlevel.service 7ms sys-fs-fuse-connections.mount 1ms sys-kernel-config.mount Version-Release number of selected component (if applicable): Installed Packages Name : dmraid Arch : x86_64 Epoch : 0 Version : 1.0.0.rc16 Release : 30.fc24 Size : 331 k Repo : @System From repo : @commandline How reproducible: Unsure. Actual results: Long boot times. Expected results: Normal boot times. Additional info: My system has been upgraded a couple of releases from f22 I think. It doesn't have any raid devices setup.