When should I run fsck and tune2fs?

[d-pupp]

Please help me understand when and how often to run fsck.
It is in my boot parms from menu.lst

Code: Select all

psubdir=/vanilla10 pmedia=atahd pfix=fsck

However the output of tune2fs seems to show it hasn't ran since I set the system up.

Code: Select all

Filesystem created:       Fri Sep 23 14:01:37 2022
Last mount time:          Fri Apr 17 15:31:54 2009
Last write time:          Fri Apr 17 15:31:54 2009
Mount count:              831
Maximum mount count:      -1
Last checked:             Fri Sep 23 14:01:37 2022
Check interval:           0 (<none>)

The way I'm reading this
Max mount count -1 means disabled check after xx number of mounts
Check interval 0 (<none>) means disabled scheduled check interval

So how does this work? My understanding it fsck will not run at boot up if the system is marked clean but how does it know that if it never runs? Or does it do a quick scan on every boot?

Edit
Vanilladpup 10.0.48 wayland
filesystem is ext4

[Jasper]

@d-pupp

Sorry, I cannot tell you when it needs to be run. However, it is always just good 'general housekeeping' to ensure to make your OS is running well.

The only time I have had to invoke this (........... tell a lie it runs itself) is when there is a problem ie when unmounting/ejecting a device in mid-flow.

The usual response is "F*ck" and during boot up it runs itself.

This has been my experience using external USB flash/HDD drives.

Not much help, I guess

Why not just schedule a run when you feel that it requires it for "peace of mind" ?

Apart from taking the time for it to run, what harm can it do?

[bigpup]

pfix=fsck -> do filesystem check on save (and host partition)

so it is only making sure the file system in the save is still good and partition it is on file system.

I have seen it pop up a report message during the boot process if it finds a problem and then fixes it.
This is usually if you use a save file with ext2 file system in it. (save.2fs)
Ext2 is easy to get corrupted, so that was main reason to have pfix=fsck boot option.

Not sure this ever gets recorded any place.