Bug 368 - fsck forced unnecessarily
Summary: fsck forced unnecessarily
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 5.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1998-12-09 19:12 UTC by john.wiersba
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1998-12-09 19:31:01 UTC

Attachments (Terms of Use)

Description john.wiersba 1998-12-09 19:12:09 UTC
Occasionally, when rebooting after a clean shutdown, I get
the following boot sequence for all my volumes:
 [/sbin/fsck.ext2] fsck.ext2 -a /dev/hdb8
  /dev/hdb8 has reached maximal mount count, check forced
  /dev/hdb8: 31/256000 files (0.0% non-contiguous), ...

Obviously, this is not good (it takes a long time, too).  It
doesn't seem to be related to anything I did while I was
running before shutting down.  What is this "maximal mount

Comment 1 David Lawrence 1998-12-09 19:31:59 UTC
This is acually a feature of the Linux operating system.  What is
happening is that the system is reaching a mixmal count for the number
of times that a file system has been mounted.  Once that count is
reached, the system performs a filesystem check to verify that
everything is functioning well with the filesystem. Just call is
preventative maintenance.  Anyway, the number of mounts before this
happens is set in the fstab file.  Check out the man page for fstab is
you would like to alter the number of mounts before the system check
is performed.

Comment 2 Aleksey Nogin 1998-12-09 23:28:59 UTC
I believe, the max mount count is set by tune2fs -c, not by /etc/fstab

Comment 3 David Lawrence 1998-12-10 17:25:59 UTC
You are correct. That was our error. You do need to use the tune2fs
command for altering the amount of times between two mounts to run
fsck on the partition. The last two numbers of each line in fstab are
for the dump utility and the order to mount the partitions during boot

Note You need to log in before you can comment on or make changes to this bug.