Bug 1398238 - [RFE] Ability to have an option to do fsck -y on boot
Summary: [RFE] Ability to have an option to do fsck -y on boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1298243
TreeView+ depends on / blocked
 
Reported: 2016-11-24 10:34 UTC by Andrea Perotti
Modified: 2020-07-16 09:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-24 14:52:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrea Perotti 2016-11-24 10:34:47 UTC
1. Proposed title of this feature request
Ability to configure RHEL to do automatic fsck -y if needed

3. What is the nature and description of the request? 
We have a large environment of VM, and sometimes the cluster crash.
When the cluster (4000 Linux Boxes) crash we need to login into every host and perform fsck -y on all of the hosts with fsck problems.

4. Why does the customer need this? (List the business requirements here)
- We are making use of Cyberark - tons of different password, only root can login into the systems in this situation.
- We need to ensure the less time possible to restart the environment
- We take the responsability of the eventual problem that may happens after fsck -y.

5. How would the customer like to achieve this? (List the functional requirements here)
Modification in grub to add this automatic fsck by default.
Would be useful to add also a secondary entry for grub to to fsck "on demand" selecting grub entry (not default).

6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
1) crash one server
2) reboot and have fsck -y performed automatically without password asking

8. Does the customer have any specific timeline dependencies?
6month from now

9. Is the sales team involved in this request and do they have any additional input?
no 

11. Would the customer be able to assist in testing this functionality if implemented?
Yes, sure

Where are you experiencing the behavior?  What environment?

RFE

When does the behavior occur? Frequently?  Repeatedly?   At certain times?

RFE

What information can you provide around timeframes and urgency?

RFE

Comment 2 Kamil Dudka 2016-11-24 10:49:50 UTC
This has nothing to do with the filesystem package.  Switching to systemd although I suspect that such an option is already available (via fsck.mode and fsck.repair parameters accepted on the kernel command line):

https://www.freedesktop.org/software/systemd/man/systemd-fsck@.service.html

Comment 5 Jan Synacek 2017-01-24 14:52:01 UTC
As stated in comment 2, this can be already achieved by specifying "fsck.mode=force fsck.repair=yes" on the kernel command line.


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