From: card@masi.ibp.fr (Remy CARD) Subject: Re: Inode/Zone count errors with ext fs Date: Sat, 14 Nov 1992 18:43:37 GMT
In article <1992Nov14.151002.23536@mintaka.lcs.mit.edu> wyvern@hal.gnu.ai.mit.edu (The Wyvern) writes:
>
> I recently upgraded to Linux v0.98pl4. Everything seems to work great,
>except for some strange errors I'm receiving from efsck for my ext fs
>partition. After reboot I did an efsck /dev/hda4 and got these errors:
> Free inodes count wrong (13193, counted=13194).
> Free zones count wrong (36297, counted=36317).
>efsck -r doesn't seem to fix the problem - I've tried it several times.
>Is there any way to get rid of these errors short of remaking the whole
>filesystem?
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.
Remy