David Stuart wrote:
Thanks Alan and Mark,
I think I'll leave things as they are for now. But now I know they're
considered normal.
Thanks,
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
[EMAIL PROTECTED]
"Mark Post" <[EMAIL PROTECTED]> 8/20/2007 4:34 PM >>>
On Mon, Aug 20, 2007 at 7:26 PM, in message
<[EMAIL PROTECTED]>, David Stuart <[EMAIL PROTECTED]>
wrote:
-snip-
During a reboot this afternoon, I received a message stating that it had
been 143 days since /dev/dasd?1 had been checked. Check forced.
-snip-
Is this normal? I don't remember ever seeing this before, even when it had
been several months since the prior reboot.
Yes, the EXT2 and EXT3 file systems (and probably all file systems) do this.
If you're using EXT3, you can do a:
tune2fs -c0 -i0 /dev/dasd??
to turn that off. There are two switches you need to specify because there are
two counts that are kept:
1. Number of days since the last file system check
2. Number of file system mounts since the last file system check
I would _not_ recommend doing this on an EXT2 file system, unless you always
have it mounted read-only.
These days I wouldn't recommend using ext2.
Some recommend turning it off to avoid unexpectedly long boot times: I
have reconfigured the system and now reboot just to be sure it's okay.
And then it takes eons to come up and my downtime balloons....
There is the complementary recommendation to schedule time to run the
fsck. Depending on the filesystem, the system might not need to be down
for the check.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
