Comment 2 for bug 219382

Mounting a "dirty" root file system without fsck is a dangerous feature. It negates the benefits of journaling file systems (fast fsck on unclean shutdown).

I think I understand how this "fix" came to be (people were complaining about the forced periodic fsck on ext3), but the hammer is too big.

The initscripts need to distinguish fsck's due to ext3's maximum mount count from fsck's due to a dirty file system.