Bug 42228 - maximal mount count, check forced
maximal mount count, check forced
Product: Red Hat Linux
Classification: Retired
Component: filesystem (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-05-24 21:32 EDT by philip dahlquist
Modified: 2014-03-16 22:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-06-22 11:24:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
boot log from install date to present, 3 days old (138.57 KB, text/plain)
2001-05-24 21:45 EDT, philip dahlquist
no flags Details

  None (edit)
Description philip dahlquist 2001-05-24 21:32:27 EDT
Description of Problem:
maximal mount count, check forced.  during bootup, in the checking section
[ok], the filecount max is reached, then the whole harddrive is scanned
while a percentage is displayed.  this happens approx. 3 or 4 days after
1st installation, and then every 3 or 4 boot up day, until an X windows log
file can't be opened for writing, and X Windows won't start, and then, the
next boot inevitably won't work, i'd have to re-install.

How Reproducible:
i don't know how it is reproduced

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
this happened with rh7.0, as well.

if you need to call me, i can be reached at 202-543-2185 day and evening

philip dahlquist
Comment 1 philip dahlquist 2001-05-24 21:45:26 EDT
Created attachment 19570 [details]
boot log from install date to present, 3 days old
Comment 2 Bill Nottingham 2001-05-25 11:20:59 EDT
What are the error messages from X?

A fsck is forced every 20-25 mounts or so; this is normal.
Comment 3 Michael Schwendt 2001-06-15 15:16:10 EDT
Try increasing the maximal mount count using "tune2fs -c VALUE /dev/YOURDEVICE".
I bet you'll see that the problem with X is not related to the fsck.

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