Bug 11 - shutdown -F failsfr works
Summary: shutdown -F failsfr works
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 5.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
URL:
Whiteboard:
: 694 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1998-11-09 16:30 UTC by David Lawrence
Modified: 2016-07-05 14:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 05:00:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Derek Tattersall 1998-11-09 16:30:49 UTC
shutdown -F should write a file, /forcefsck which should
then be looked at by the boot proces to force an fsck.
According to Dr Mike, it did this in 5.1, but does it not
in 5.2.  There are other ways to accomplish the aim, but
right now the shutdown man page says that -F will force a
check and it doesn't.

Comment 1 Bill Nottingham 1999-01-05 20:14:59 UTC
*** Bug 11 has been marked as a duplicate of this bug. ***

'shutdown -F' touches /forcefsck in order to force an fsck
of all filesystems on reboot.  The init scripts should
notice this file and execute the fsck -- they do not.  It is
currently impossible to force an fsck of all filesystems at
boot time.  This functionality is insensive to the
filesystem type.  This functionality worked on a previous
version of
RedHat.

There is a reference to a /fsckoptions file in the init
scripts, but this file is almost useless as it passes its
options to all filesystems which is generally not
appropriate.

Comment 2 Bill Nottingham 1999-02-05 17:35:59 UTC
should be fixed in initscripts-3.84.

Comment 3 Fedora Update System 2016-06-22 02:23:28 UTC
softhsm-2.1.0-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-40cd1f94ba

Comment 4 Fedora Update System 2016-06-22 12:32:49 UTC
softhsm-2.1.0-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c43dd0091f

Comment 5 Fedora Update System 2016-06-22 12:33:11 UTC
softhsm-2.1.0-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-376bda6d1d

Comment 6 Fedora Update System 2016-06-22 22:56:27 UTC
softhsm-2.1.0-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-40cd1f94ba

Comment 7 Fedora Update System 2016-06-22 22:59:28 UTC
softhsm-2.1.0-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c43dd0091f

Comment 8 Fedora Update System 2016-06-22 23:02:34 UTC
softhsm-2.1.0-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-376bda6d1d

Comment 9 Fedora Update System 2016-07-05 05:00:03 UTC
softhsm-2.1.0-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2016-07-05 08:25:31 UTC
softhsm-2.1.0-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2016-07-05 14:22:12 UTC
softhsm-2.1.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.