From: curtis@cs.berkeley.edu (Curtis Yarvin) Subject: Re: Inode/Zone count errors with ext fs Date: 15 Nov 1992 06:56:50 GMT
In article <1992Nov14.184337.23031@jussieu.fr> card@masi.ibp.fr (Remy CARD) writes:
>
> The problem here is that you surely check a mounted file system.
>When efsck corrects some problems, it corrects them on the disk but this
>does not modify the copy of the super block kept in memory. When the
>file system is unmounted or when the fs are synced, the memory copy of
>the super blocks is written back to the disk and the modifications made
>by efsck are lost. To correct your ptoblem, you need to first unmount
>the file system and the check it with efsck. If your file system is
>the root file system, you cannot unmount it so you must boot with a floppy
>as the root fs and the check your disk partition.
Why not just reboot immediately after checking?
This is what most Unixes do.
I strongly suggest the people who are creating load packages include
a standard shutdown/rc that does this; the root filesystem should
definitely be checked after every uncontrolled reboot, and a system
which does not do this can lead to much grief and tearing of hair
on the part of people who don't know enough to fix their own filesystems.
c