Hya

To whom it may concern.

I knew that -F option for shutdown command was removed.
I did not know that /forcefsck was obsolete.

I needed to check file system integrity. So, I didI checked that /forcefsck was gone after reboot.

BUT fact is that file check was NOT performed.

Why I noticed? shows that file system check was done almost two years ago and that several hundred mount times since then.

system: Debian testing amd64

You can set how often the fsck is done with tune2fs itself. Run "man tune2fs" and look at the "-c" (count) and "-i" (interval) options.

If they've not been checked in 2 years it seems likely someone disabled the default count and interval. Some people do this to prevent large filesystems (e.g. those used for databases) being automatically checked on reboot because for ext2 and ext3 that could take a while. For ext4 it usually is fairly painless. If you DO disable automatic fsck then you should have a schedule to manually run it periodically. You also should only do such disabling for large filesystems like data and not for your root and other system filesystems. If everything is in root filesystem and you don't want to wait for fsck to finish you should seriously consider re-ordering things so that data is not in root filesystem any longer.

You don't say whether your running ext2, ext3 or ext4. As noted fsck for ext4 is generally quick and painless so there is little reason to disable automatic checks even for large data filesystems.

Hya,

Thanks. My penguins look better now. The file system used on this one is ext4.
By the way, I do not see much reason for these fsck related changes.

cheers