INCORRECT BLOCK COUNT and UNALLOCATED errors

[Woodchuck]

On Thu, 2 Nov 2006, Lou Hevly wrote:

> But then I restarted Apache and I got errors again.

I don't think you can run fsck on a mounted filesystem and ~not~
get errors.  chrooted apache will doubtless have activity on /var.
(Also syslogd will, too, at least intermittently).

I wouldn't pay attention to errors found by fsck on a mounted system.

> >However,  you will need to isolate the system and perhaps kill various
> >processes. (Those with files open on /var or whatever filesystem you
> >are fsck'ing).   Do not be umounting /var or /home on a system with
> >random users and processes.  You want a quiet system.
> 
> My system is pretty calm.

You want it completely calm ;-)

Use fstat to see if anything is opened on a filesystem, then umount
it before fsck'ing.

SYSV style init had "runstates", one of the ones BSD doesn't have
kicked off all users except root from interactive sessions and killed
off daemons.  But I believe this state also closed the network.  You'd
like the system to be in a state in which only root can have an interactive
process, all daemons were killed, but in which enough networking was
up so that you could allow the ssh process of root to endure. 

Dave
-- 
       Of a truth, few men desire freedom, the greater part
           are content with just masters. --  Sallust