[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]
Re: [LI] Maximal count reached
On Mon, 4 Oct 1999, Binand Raj S. wrote:
> /dev/hda5 has gone too long without being checked .. check forced?
There are a number of parameters u can configure with tune2fs.
Maximum Mount counts: Max. number of times a file system is mounted
before it is forced to be fsck'ed.
Interval Between Checks: Time interval between two successive calls to
fsck for the same file system.
So, as one can see that these two parameters are different.
These parameters on my machine are:
Filesystem volume name: root
...
Last mount time: Mon Oct 4 15:38:54 1999
Last write time: Mon Oct 4 18:49:29 1999
Mount count: 1
Maximum mount count: 10
Last checked: Mon Oct 4 15:36:48 1999
Check interval: 1209600 (2 weeks)
Next check after: Mon Oct 18 15:36:48 1999
What this means is that if I mount/unmount this device more than 10
times in a 2 week period, when I try to mount it the 11th time, I will
get the "Maximal Count Reached" message.
OTOH, if I keep my machine on for > 2 weeks, it doesn't crash and I
don't fiddle with the file system, then on the next boot fsck will be
forced because of the time interval parameter!
hope this clears this stuff up!
regards,
sachin
Hubbard's Law:
Don't take life too seriously; you won't get out of it alive.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sachin Garg, Member Technical Staff
Centre for Development of Advanced Computing,BANGALORE,INDIA
Phone: +91-80-5584271/143/982 Fax: +91-80-5584893
http://sangam.cjb.net <sachin@xxxxxxxxxxxxxx>
--------------------------------------------------------------------
For more information on Linux in India visit http://www.linux-india.org/
The Linux India mailing list does not accept postings in HTML format.