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:
When both /.autorelabel and /forcefsck files are created and machine rebooted, fsck is performed twice due to design of /etc/rc.d/rc.sysinit file. In case of large filesystems with a lot of files it unnecessarily prolonges downtime.

The issue lies in fact that first fsck part is performed first, then selinux relabel comes and reboot. While the part of script responsible for relabeling removes the file /.autorelabel; the /forcefsck remains untouched and causes second filesystem check upon next statup


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


How reproducible:
easily reproducible


Steps to Reproduce:
1. touch /forcefsck /.autorelabel; reboot

Actual results:
Filesystem check performed unnecessarily twice, time loss, downtime prolonged.


Expected results:
Filesystem check should be done once. My recommendation: rewrite rc.sysinit scipt thai it remove /forcefsck right after the check finishes.

Basesystem is just dependency metapackage with no content. Reassigning to initscripts and adding Keyword SELinux. Lukas, please reassign to proper component if initscripts doesn't handle SELinux part.

Should be easy to fix.

https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel6-branch&id=41bc9f110d7b3f1e3b762fc879bc6e13c5bfad42

Patch looks sane.

$ touch /forcefsck /.autorelabel; reboot

with initscripts-9.03.49-1.el6
1. /sbin/fsck -T -t noopts=_netdev -A -a -C -F
2. selinux relabel
3. reboot
4. /sbin/fsck -T -t noopts=_netdev -A -a -C -F

with initscripts-9.03.51-1.el6
1. /sbin/fsck -T -t noopts=_netdev -A -a -C -F
2. selinux relabel
3. reboot
4. /sbin/fsck -T -t noopts=_netdev -A -a -C

Works as expected

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0951.html