Bug 1039200

Summary:	Journal flushing often slow, can prevent system booting correctly
Product:	[Fedora] Fedora	Reporter:	Scott Schmit <i.grok>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	ahmadsamir3891, alexhultman, alick9188, awilliam, bob53181, collura, harald, ignatenko, i.grok, johannbg, jreznik, kvolny, lnykryn, michele, mlichvar, mruckman, mschmidt, msekleta, plautrba, pschindl, rdieter, robatino, selinux, systemd-maint, theo148, tomek, vpavlin, yaroslav.sapozhnik, yjcoshc, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AcceptedBlocker
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1006386	Environment:
Last Closed:	2015-01-09 21:05:49 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:
Embargoed:

Description Scott Schmit 2013-12-06 21:39:42 UTC

The below bug also affects Fedora 19.

+++ This bug was initially created as a clone of Bug #1006386 +++

Description of problem:
Running latest Rawhide, x86_64 system.

Booting with /var/log/journal existing takes 27 seconds longer that when I boot with no /var/log/journal: I did "mv /var/log/journal /var/log/journal.old" just before reboot).

Booting without /var/log journal reports taking 25.4 seconds.
Booting with /var/log/journal reports taking 52.0 seconds.

[These are consecutive reboots, about 2 minutes apart.]

This occurs every time I boot with /var/log/journal.

I finally got booting with "systemd.log_level=debug" to work: appears I also needed "debug" as a kernel commandline option.

I attach the output of "journalctl -o short-monotonic -ab" and "systemctl analyze plot" booting both without /var/log/journal and then booting with /var/log/journal.

Version-Release number of selected component (if applicable):
systemd-206-11.fc21.x86_64
kernel-3.12.0-0.rc0.git16.2.fc21.x86_64
dracut-032-23.git20130904.fc21.x86_64

How reproducible:
Every boot....

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

...

--- Additional comment from Petr Schindler on 2013-12-04 11:51:16 EST ---

I updated to systemd-208-8.fc20 and it seems to work quite fine. At least it boots now to gdm.

--- Additional comment from Fedora Update System on 2013-12-04 19:37:40 EST ---

Package systemd-208-8.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-208-8.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-22704/systemd-208-8.fc20
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-12-06 00:55:59 EST ---

systemd-208-9.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 1 Lennart Poettering 2015-01-08 01:58:32 UTC

*** Bug 983688 has been marked as a duplicate of this bug. ***

Comment 2 Fedora End Of Life 2015-01-09 20:48:18 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 3 Adam Williamson 2015-01-09 21:05:49 UTC

as 19 is now EOL and later releases were fixed, nothing to be done here.