Bug 414141

Summary:	fsck of all disk filesystems in /etc/fstab even though clean
Product:	Red Hat Enterprise Linux 4	Reporter:	Nick White <nghwhite>
Component:	initscripts	Assignee:	initscripts Maintenance Team <initscripts-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-12-06 16:23:03 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 Nick White 2007-12-06 15:33:25 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Description of problem:
If external filesystems are manually unmounted cleanly prior to a shutdown/reboot but the root filesystem does not shutdown cleanly for whatever reason, on the subsequent hard reboot pressing "Y" to clean the root, boot, var, usr and tmp filesystems results in all the external filesystems being fsck'd even though they were clean, within their check date and check count.

This has been reproduced consistently using an Infortrend array but happens with any external hardware array(3Ware or Areca). The rc.sysinit file sets the --f flag to fsck when "Y" is pressed and then runs through all the filesystems in /etc/fstab with that flag set so the external filesystems that were cleanly unmounted get cleaned. This is extremely time consuming on systems with 6 to 10 TB.

Version-Release number of selected component (if applicable):
initscripts-7.93.29.EL-1

How reproducible:
Always

Steps to Reproduce:
1. Create a filesystem on an external array
2. Add the external array/filesystem to /etc/fstab
3. mount -a
4. unmount external filesystem
5. Power cycle the system so the root filesystem is dirty
6. During boot when asked whether root filesystem should be checked, press <Y>
7. Once root, boot, var, tmp, usr etc have been checked, the external filesystem will be checked.

Actual Results:
fsck was performed on the external array/filesystem despite the fact that it had been cleanly unmounted prior to the shutdown/reboot.

Expected Results:
The check in rc.sysinit should check whether the external filesystem is clean, within date and count and only then run fsck against the filesystem or use another
option to clean ALL disk filesystems in /etc/fstab or just root, boot, var, tmp and usr.

Additional info:

Comment 1 Bill Nottingham 2007-12-06 16:23:03 UTC

The option is to force 'file system check' - this option is for all file systems
in /etc/fstab, not for clean vs. unclean filesystems.

Comment 2 Nick White 2007-12-06 16:34:17 UTC

Can an enhancement be considered for an option to clean only unclean filesystems
as well as keeping existing functionality?

Comment 3 Bill Nottingham 2007-12-06 16:53:30 UTC

The option/prompt isn't actually there in later RHEL releases, so, no.

Comment 4 Nick White 2007-12-06 17:00:46 UTC

In which release does the option/prompt vanish and what is the default behavior?

Comment 5 Bill Nottingham 2007-12-06 17:23:59 UTC

In RHEL 5 the prompt is not there. You have to manually force a filesystem check
on boot (or have a non-journaled filesystem that is dirty.)