{{{I don't know if this question "belongs" in this thread, because it concerns filesystems, a command, and software... so if this thread is not the place it should be in.... tell me I am a {butt}hole and I will apologize}}}

Last night, I discovered why on a ext4 filesystem the command "touch /forcefsck" doesn't work as expected.

Yeah, I have been using the ext4 filesystem since around 2008.

I know the solution is to change/write

GRUB_CMDLINE_LINUX="fsck.mode=force"

in the file /etc/default/grub and do an "update-grub" {or update-grub2}

And it now works as expected..... BUT....

Suppose I don't want to force an fsck on all of my filesystems every time I reboot?

Yeah... I know I can do a CTRL-c and stop the process.

QUESTION:

Is there any other way to NOT force a fsck on all my filesystems every time I reboot OTHER than edit that file and do an update?

I would guess that the answer is "NO", but just asking just in case there might be a better solution.

Thank you for your time and have a great day!

As I understand how things work specific to linux filesystems.

Normal automatic fsck checks happen as defined when the filesystem was created or as configured. If the 6 column (fsck) value is greater then 0 the filesystem will be checked at start based on last check, number of mounts or unclean unmount.

On SySV init systems you can force a fsck at boot time by creating a dummy file named forcefsck in the / directory. After fsck is finished the forcefsck file is deleted.

On systemd init systems you need to add a command line parameter fsck.mode= which can be either auto, force or skip. which is passed to systemd-fsck service.

I have not tried lately but you should be able to manually edit the boot command line from the grub menu either to delete or add a kernel parameter.

Thank you for your reply, michaelk.

I'll read up on the parameters {auto/force/skip} for fsck.mode.

Maybe that will get me what I need to know.

Have a good day!