Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After an improper shutdown in a server of a client of mine, /boot and / filesystems were not properly unmounted.
On system boot we get:
Your system appears to have shut down uncleanly
Press Y within 1 seconds to force file system integrity check...
Our client didn't press anything. The system didn't do an fsck. It tried to boot and failed. Our client pressed [CTRL]+[ALT]+[DEL]. The system performed a reboot and on that second boot, everything seemed OK.
The server started operating again for some time. After a while the / filesystem became completely inconsist and we have to bring it back from a backup.
Version-Release number of selected component (if applicable):
RHEL6.1
How reproducible:
The above situation happened due to a combination of a power failure and a malfunctioning UPS.
Steps to Reproduce:
1. On a RHEL server, press the 'reset' (hardware) button.
2. During the reboot, DO NOT press 'Y'.
3. Make a second (proper) reboot.
4. All filesystems are now seem to be OK!
5. A filesystem inconsystency is possible to happen rigth ahead...
Actual results:
A filesystem inconsystency is possible to happen quite soon.
Expected results:
The OS should have started a filesystem check and ask user only for a modification.
Additional info:
We had come across exactly the same issue in RHEL4, some years ago.
We believe that /etc/sysconfig/autofsck file with parameteres like AUTOFSCK_DEF_CHECK=yes and AUTOFSCK_TIMEOUT=<some_time> should be the default in RHEL installation.
We do not force a check on unclean shutdown - we let fsck replay the journal when necessary. This has been the default in RHEL 4/5/6, and is not going to change in a minor release. As you note, this can be done with configuration.