I have some quick questions concerning "tune2fs" and "e2fsck.*"
 

First: I have checked on linuxquestions.org and have an answer.... I think... so I am just checking if I understand the answer.

==============

Question 1:

I did a "touch /forcefsck" and when I did a reboot, it behaved as normal. About a week later, I had read that the "touch /forcefsck" had been deprecated, and that I should insert a similar command in the grub configuration.

Apparently, "forcefsck" still works properly.

WHAT'S UP WITH THAT???

==================

Question 2:

On "tune2fs" if I set an interval AND a mount amount, will it honor BOTH parameters?

That is, if either the interval OR the mount amount parameter "triggers" it will do a fsck and reset both numbers (interval and mount amount).

Is that correct?

======================

Just checking if I understand what I have read.

Thank you for your response.

Have a good day.

In answer to your questions

1. Go with the flow
2. Yes it should.

1.

forcecheck was convention, implemented in init scripts. Maybe it it still honoured by your distro, maybe not on others.
As for interval driven ext? fsck, that has all been ignored for years unless you specifically override it in mke2fs.conf. E2fsprogs now checks at every mount, and runs fsck as needed.