Kernel Errors...!!! Help newbie


Active Member
Jun 2, 2004
Recently, I have got this on LogWatch. Anyone knows what this means?
CentOS 3.4 v2.4.21-27.0.2.ELsmp

176 Time(s): Advised path = 72.*.*.* -> 217.*.*.198, tos 04
1 Time(s): EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
1 Time(s): EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
1 Time(s): EXT3-fs: mounted filesystem with ordered data mode.
176 Time(s): Redirect from 217.*.*.197 on eth0 about 217.*.*.198 ignored.
1 Time(s): kjournald starting. Commit interval 5 seconds



Well-Known Member
May 29, 2004
Minneapolis, MN
The reason why the kernel is reporting the maximal mount count even after e2fsck is run because e2fsck is accessing the partition via the LVM device, because your /etc/fstab file specified /dev/discs/disc0/part1. However, the kernel is accessing the filesystem via IDE device /dev/hda1. This is a really bad thing, since it means that buffer cache can get out of sync.

The "mount" command gets its idea of what is mounted via the /etc/mtab file. But the root filesystem is mounted during the kernel boot process, before the init scripts are run. Also, the root filesystem is mounted read-only until after e2fsck is run. So after the root filesystem is checked, and then remounted read-write, the init scripts initializes the /etc/mtab file using data from the /etc/fstab file. If the information in /etc/fstab is not accurate (i.e., is not the same as the root filesystem specified on the kernel command line when it was booted), then the information in /etc/mtab isn't accurate, which means that what the 'mount' command prints won't be accurate.

First, you need to make sure the /etc/fstab's idea of the root device matches what is used on the kernel command line. Secondly, the periodic maximum mount checks are normal. You can turn it off using tune2fs if you wish, if you're willing to live with the potential consequences. (Note: these issues are present regardless of what filesystem you use; it just that some filesystems are designed assuming that disk drives are perfect, whereas ext2/3, given that it was born on PC hardware, has some design choices and defaults which are a bit more paranoid about trusting the underlying hardware.)

Unless you know what you are doing, otherwise contact your NOC and ask them to correct this problem.