Resolved: How to correct "maximal mount count reached" error?

[kjcsb]

> > Jun  9 14:49:28 conversant01 kernel: EXT3-fs warning: maximal mount 
> > count
> > reached, running e2fsck is recommended
>
> As it suggests, you should run fsck periodically.
> shutdown -F will force a fsck of all partitions on the next reboot.
>
I did this and was still getting the error.
Jun 10 06:43:33 conversant01 kernel: EXT3 FS on sda1, internal journal
Jun 10 06:43:33 conversant01 gpm[3191]: *** info [startup.c(95)]:
Jun 10 06:43:33 conversant01 kernel: EXT3-fs: mounted filesystem with 
ordered data mode.
Jun 10 06:43:33 conversant01 gpm[3191]: Started gpm successfully. Entered 
daemon mode.
Jun 10 06:43:33 conversant01 kernel: kjournald starting.  Commit interval 5 
seconds
Jun 10 06:43:33 conversant01 kernel: EXT3-fs warning: maximal mount count 
reached, running e2fsck is recommended

I'm not sure, but it seems to be complaining about sda1. However:
[root at conversant01 ~]# tune2fs -l /dev/sda1
<snip>
Mount count:              1
Maximum mount count:      10
</snip>

[root at conversant01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              66G   51G   13G  81% /
/dev/sda1              99M   61M   34M  65% /boot
none                  505M     0  505M   0% /dev/shm
/dev/sdc1             8.3G  2.2G  5.7G  28% /diskimages

[root at conversant01 ~]# fdisk -l

Disk /dev/sda: 8984 MB, 8984199168 bytes
255 heads, 63 sectors/track, 1092 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        1092     8667067+  83  Linux

Disk /dev/sdb: 72.7 GB, 72725037056 bytes
255 heads, 63 sectors/track, 8841 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1        8711    69971076   83  Linux
/dev/sdb2            8712        8841     1044225   82  Linux swap / Solaris

Disk /dev/sdc: 8984 MB, 8984199168 bytes
255 heads, 63 sectors/track, 1092 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        1092     8771458+  83  Linux

Further investigation reveals that fsck is only checking certain devices:
/dev/sda1 checked
/dev/sda2 not checked
/dev/sdb1 checked
/dev/sdc1 not checked

It seems to be only checking Boot devices. So:
[root at conversant01 ~]# fsck /dev/sda2
...
[root at conversant01 ~]# tune2fs -l /dev/sda2
<snip>
Mount count:              0
Maximum mount count:      10
</snip>

[root at conversant01 ~]# umount /diskimages
[root at conversant01 ~]# fsck /dev/sdc1
...
[root at conversant01 ~]# tune2fs -l /dev/sdc1
<snip>
Mount count:              1
Maximum mount count:      10
</snip>

Regarding sdb2:
[root at conversant01 ~]# tune2fs -l /dev/sdb2
tune2fs 1.38 (30-Jun-2005)
tune2fs: Bad magic number in super-block while trying to open /dev/sdb2
Couldn't find valid filesystem superblock.

I guess the swap file is irrelevant!

I rebooted and the error no longer appears.

Thanks for your help.

Cameron