Why does fsck check more often than every 30 mounts

Hello...Ext2fs and ext3fs force a filesystem check after a specified number of mounts or a specified amount of time between mounts. The idea is to catch errors that might creep onto the filesystem due to random disk write errors or filesystem driver bugs. You can change these intervals by using the -c max-mount-counts and -i interval-between-checks options to tune2fs. For the latter option, you specify an interval in days, weeks, or months by providing a number followed by a d, w, or m, respectively. Altering the check interval won't modify day-to-day performance, but it will change how frequently the computer performs a full disk check on startup. This disk check can be quite lengthy, even for ext3fs; it doesn't restrict itself to recent transactions as recorded in the journal, as a forced check after a system crash does. Its not a bug i think so..
Regards,
Bhavani Shankar.

I don't know what the default amount of time is but I'm betting it's more than 20 days. I boot each day so I would expect my system to force a check after 30 mounts (the ubuntu default) or so. It never waits for 30. It's always doing it at 28 or 21 or 18. If it's supposed to wait for 30 mounts then why does it do it sooner? I can play with tune2fs but unless there is a bug in how ubuntu sets this up I can't imagine how that will help. I suppose I could set it to 40 mounts and then it would probably do it around 30 but that seems a bit ridiculous.

I don't know what the default amount of time is but I'm betting it's more than 20 days. I boot each day so I would expect my system to force a check after 30 mounts (the ubuntu default) or so. It never waits for 30. It's always doing it at 28 or 21 or 18. If it's supposed to wait for 30 mounts then why does it do it sooner? I can play with tune2fs but unless there is a bug in how ubuntu sets this up I can't imagine how that will help. I suppose I could set it to 40 mounts and then it would probably do it around 30 but that seems a bit ridiculous.

Maybe the 30 mounts is not the only criteria? I could be also that the system spots a problem somewhere and force a check at next boot? Maybe you should go for a very detailed check of the disk to see if everything is alright.

I could do that. How does one do a "detailed" check? However, I don't have any indication that there are problems and the drives were recently replaced anyway. This issues existed on the "old" drives and still exists on the new drives. I don't see this just on one computer either. It seems to do it on every computer I use. Am I the only one who sees this? That would point to a problem on my systems.

Yes.. How to do a detailed check...? I think I have given all the parameters with the commands.... I also bet that its more than 20 days... Btw I upgraded my system and fsck is showing an error in my original and backup blocks of my HDD and doing a check everytime.... It wasnt there in my old system and it happens only in gutsy and feisty... as a result system starts slowly......Now I think its a bug... Thanks Jim....
Bhavani Shankar.

An alternative idea:
https://wiki.ubuntu.com/AutoFsck