home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!sgiblab!zaphod.mps.ohio-state.edu!usc!rpi!crdgw1!rdsunx.crd.ge.com!ariel!davidsen
- From: davidsen@ariel.crd.GE.COM (william E Davidsen)
- Newsgroups: comp.os.linux
- Subject: Re: Inode/Zone count errors with ext fs
- Keywords: extfs
- Message-ID: <1992Nov17.221600.7386@crd.ge.com>
- Date: 17 Nov 92 22:16:00 GMT
- References: <1992Nov14.151002.23536@mintaka.lcs.mit.edu>
- Sender: usenet@crd.ge.com (Required for NNTP)
- Reply-To: davidsen@crd.ge.com (bill davidsen)
- Organization: GE Corporate R&D Center, Schenectady NY
- Lines: 25
- Nntp-Posting-Host: ariel.crd.ge.com
-
- 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?
-
- On most version of UNIX and its clones, an fsck on an active f/s is
- likely to produce some warnings. The suggested way to do it is to
- unmount the f/s before checking. On Linux this means boot from floppy
- for the root partition.
-
- I do this for backup of some systems, too. All partitions other than
- root are backed up unmounted in single user mode, root is backed up
- booted from another partition (need not be floppy). Of course I do
- running dumps of stuff, too, but the dumps I really trust are done on an
- unmounted f/s.
-
- --
- bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
- Keyboard controller has been disabled, press F1 to continue.
-