Bug 42228

Summary: maximal mount count, check forced
Product: [Retired] Red Hat Linux Reporter: philip dahlquist <dahlquist>
Component: filesystemAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: Aaron Brown <abrown>
Severity: high Docs Contact:
Priority: medium    
Version: 7.1CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-06-22 15:24:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
boot log from install date to present, 3 days old none

Description philip dahlquist 2001-05-25 01:32:27 UTC 
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:
1. 
2. 
3. 

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-25 01:45:26 UTC 
Created attachment 19570 [details]
boot log from install date to present, 3 days old
Comment 2 Bill Nottingham 2001-05-25 15:20:59 UTC 
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 19:16:10 UTC 
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.