Bug 757770

Summary:	systemd gets confused by fsck
Product:	[Fedora] Fedora	Reporter:	Dan Winship <danw>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	johannbg, johannbg, lpoetter, metherid, mschmidt, notting, plautrba, systemd-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-14 15:36:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dan Winship 2011-11-28 16:45:55 UTC

While booting, my laptop decided that it was time for an fsck. Time passes. Then suddenly, systemd decides that the fsck has "timed out" and dumps me into emergency single-user root shell mode. There was not any real problem; it was just taking a long time to fsck my disk.

/var/log/messages from that boot has lots of kernel messages, but very little userland:

Nov 28 11:15:17 laptop kernel: [  349.173899] EXT4-fs (dm-0): re-mounted. Opts: 
(null)
Nov 28 11:15:17 laptop kernel: [  349.971958] EXT4-fs (dm-2): mounted filesystem
 with ordered data mode. Opts: (null)
Nov 28 11:15:42 laptop dbus[1480]: [system] Failed to activate service 'org.free
desktop.NetworkManager': timed out
Nov 28 11:15:42 laptop dbus-daemon[1480]: dbus[1480]: [system] Failed to activat
e service 'org.freedesktop.NetworkManager': timed out
Nov 28 11:16:04 laptop systemd-logind[1467]: Failed to start unit: Unit autovt@t
ty2.service failed to load: File exists. See system logs and 'systemctl status a
utovt' for details.
Nov 28 11:16:05 laptop systemd-logind[1467]: Failed to start unit: Unit autovt@t
ty3.service failed to load: File exists. See system logs and 'systemctl status a
utovt' for details.
Nov 28 11:16:06 laptop systemd-logind[1467]: Failed to start unit: Unit autovt@t
ty4.service failed to load: File exists. See system logs and 'systemctl status autovt' for details.
Nov 28 11:16:20 laptop systemd-logind[1467]: Failed to start unit: Unit autovt failed to load: File exists. See system logs and 'systemctl status autovt' for details.
Nov 28 11:16:21 laptop systemd-logind[1467]: Failed to start unit: Unit autovt failed to load: File exists. See system logs and 'systemctl status autovt' for details.
Nov 28 11:16:30 laptop kernel: Kernel logging (proc) stopped.
Nov 28 11:16:30 laptop rsyslogd: [origin software="rsyslogd" swVersion="5.8.5" x-pid="1524" x-info="http://www.rsyslog.com"] exiting on signal 15.


There were a lot more "timed out" messages printed to the screen, but they appear to have not been logged. I'm not sure what time corresponds to when I entered the shell and when I exited it.

After forcibly powering down (ctrl-alt-delete caused error messages to be printed, but did not reboot), the next boot was entirely without incident.

Comment 1 Michal Schmidt 2011-11-28 17:42:01 UTC

That's weird because fsck@.service has TimeoutSec=0 to disable the timeout.
Do you know if it was checking the root filesystem or another one? What filesystem type is it?

Comment 2 Dan Winship 2011-11-28 17:51:05 UTC

I guess it's possible that the timeout message I saw that I thought was about fsck was actually about something else and my brain just filled in "fsck" because I knew that's what it had been doing (and my first assumption had been that I got dumped into the shell because fsck had failed). Although that would imply that it was trying to start other services while fsck was running, which is clearly no good either.

Assuming fsck was still running, it was checking /home, having already finished the much smaller / and /boot.

Comment 3 Jóhann B. Guðmundsson 2012-01-29 20:44:06 UTC

Is this still an issue on a fully updated release or can this bug be closed?

Comment 4 Dan Winship 2012-01-30 12:41:31 UTC

I have no idea. I haven't seen the bug again, but I'm not sure I've had a forced fsck since then either.

Comment 5 Lennart Poettering 2012-09-14 15:36:55 UTC

OK, closing, since this hasn't been seen anymore. Feel free to reopen if this resurfaces.