Bug 735683

Summary:	ext2/3/4fs disk checking MUST be made verbose on boot
Product:	[Fedora] Fedora	Reporter:	Artem S. Tashkinov <aros>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	harald, johannbg, kay, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-21 18:39:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Artem S. Tashkinov 2011-09-04 23:14:01 UTC

Description of problem:

Currently if maximum mount count is reached for any extXfs and a partition needs to be "checked forced", on (re)boot systemd will run e2fsck in the *background" - and a user may think his system has frozen.


Version-Release number of selected component (if applicable): 35


How reproducible: always


Steps to Reproduce:
1. remount any ext* filesystem in rw mode N times (N ~ 33)
2. reboot
3.
  
Actual results: *even* on verbose boot there will be no indication that some FS are being checked - the system appears to be completely FROZEN


Expected results: e2fsck being verbosely run


Additional info:

Comment 1 Lennart Poettering 2011-09-21 18:39:33 UTC

This is fixed on F16. There's now a progress display on fsck.