fsck not running on max mount count

[nishtya]

I currently run kanotix as well as knoppix and on kanotix am getting a warning at boot that the maximal mount count has been reached and running e2fsck is recommended. This occurs automatically with knoppix when the max is reached but not with my kanotix install. fstab on kanotix reads:

/dev/hdb6 / ext3 defaults,errors=remount-ro 0 1

the value 1 is the same as in fstab for knoppix so getting it to run automatically must lie elsewhere and my googling is only bringing up references to setting the value above at 1, which it already is. Could someone point me in the right direction to having this run when the max count is reached?

[garyng]

don't need that for ext3. It is journaled so would be brought to consistent on mount by the background journal process which is part of the kernel and always running.

[nishtya]

Curious why does it run in knoppix after x number of mounts? I frankly always thought it a nuisance in knoppix as I dual boot 98 and have to reboot naturally more than if I just ran linux. But I figured it was necessary.

[garyng]

check under /etc/rcS.d/, standard debian calls fsck to do this kind of thing.