Forum Discussion

purna_256577's avatar
purna_256577
Icon for Nimbostratus rankNimbostratus
Jul 13, 2017

We are getting error "maximal mount count reached, running e2fsck is recommended"

We are getting error "maximal mount count reached, running e2fsck is recommended" in /var/log/kern.log, we don't see f5 is booted for 300 + days. any recommendation in f5, version is 11.x.

 

5 Replies

  • Rebooting the box may workaround the issue, but not fix it or tell you what was. I can't find any known issue with that error, at least with a quick search in askf5.

    If the error is valid, is basically saying that you reach the maximum of mounts for that mount point.

    Run these commands and it will tell you what is the mount point:

    lvscan | cut -d"'" -f2 > /shared/tmp/volumes.txt
    while read line; do echo $line && tune2fs -l $line | grep -i "Mount count" ; done < /shared/tmp/volumes.txt
    

    If nothing has passed the maximum, yes is a bug.

  • I have further checked with senior engineer , below are the findings

     

    "warning kernel: EXT2-fs warning: maximal mount count reached, running e2fsck is recommended"

     

    The BIG-IP system is counting mount times for filesystems and if it reached to maximum counts then system will log this messages in /var/log/kern.log to recommend to run e2fsck. This is just a notification that system recommend to run an e2fsck to check whether the Disk and the filesystem has problem or not when you reached maximum mount count.

     

    You may safely ignore this message as it won't affect any system operation. Or you may consider to force the BIG-IP to run a file system check. Please refer to the below solution for more details: K10328: Forcing a file system check on the next system reboot (10.x - 11.x) https://support.f5.com/csp/article/K10328

     

  • luoye's avatar
    luoye
    Icon for Nimbostratus rankNimbostratus

    Is there a KB for "The BIG-IP system is counting mount times for filesystems and if it reached to maximum counts then system will log this messages in /var/log/kern.log to recommend to run e2fsck. This is just a notification that system recommend to run an e2fsck to check whether the Disk and the filesystem has problem or not when you reached maximum mount count." ??

     

  • I have met with similar issue. I have received this answer from support:

     

    The BIG-IP system is counting mount times for filesystems and if it reached to maximum counts then system will log this messages in /var/log/kern.log to recommend to run e2fsck. This is just a notification that system recommend to run an e2fsck to check whether the Disk and the filesystem has problem or not when you reached maximum mount count.

     

    You may safely ignore this message as it won't affect any system operation. Or you may consider to force the BIG-IP to run a file system check. Please refer to the below solution for more details: K73827442: Forcing a file system check on the next system reboot (12.x - 13.x) https://support.f5.com/csp/article/K73827442

     

    Of course, you will need to reboot the system for the check to occur. Before rebooting, please backup the system to UCS and download a copy of the UCS, as per best practices.