Systems almost always fsck on reboot

Thin · 11-02-2006, 05:29 AM

Hi all

We have a set of remote systems that almost always fsck on reboot (which takes an absolute age). As most reboots are for new kernels is the following possibly relevant?

Quote:

2.10 How do I stop my system from fscking on each reboot? Dale Lutz, dal@wimsey.com

Q: How do I stop e2fsck from checking my disk every time I boot up.

A: When you rebuild the kernel, the filesystem is marked as 'dirty' and so your disk will be checked with each boot. The fix is to run:

rdev -R /zImage 1

This fixes the kernel so that it is no longer convinced that the filesystem is dirty.

Is this still an issue - it was from a very old FAQ. Are there any other settings I can check that may govern this?

TIA

Thin · 11-02-2006, 06:25 AM

We also have .autofsck in /

Is this a config file or a flag to fsck to always run? Googling seems to come up with conflicting info

gearoid_murphy · 11-02-2006, 01:25 PM

I presume you've checked the init.d scripts, particularly the checkfs script.

The /.autofsck file is created by the system automatically at boot time
by the /etc/rc.sysinit script by simply touching the file. It has no
content. The logic behind it is, that if the host went down not properly
(i.e. power loss) the /etc/rc.sysinit script will find this .autofsck
file at next boot time and the system can act with a default scenario or
like configured within the file /etc/sysconfig/autofsck. If the hosts
shuts down or reboots properly, then the .autofsck file will be erased
by the /etc/init.d/halt script and no automatic filesystem check will
happen next boot.

this config is on old systems methinks
I use debian :-)