Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!virtech!cpcahil
From: cpcahil@virtech.UUCP (Conor P. Cahill)
Newsgroups: comp.unix.i386
Subject: Re: File system problems with 386/ix
Summary: was root mounted while you were doing this?
Message-ID: <1270@virtech.UUCP>
Date: 13 Oct 89 02:07:07 GMT
References: <2462@hydra.gatech.EDU>
Distribution: usa
Organization: Virtual Technologies Inc
Lines: 29

In article <2462@hydra.gatech.EDU>, gb7@prism.gatech.EDU (Joe Bradley) writes:
> (see below). However, when I invoke fsck again, it again complains about
> the same things that it just supposedly fixed. Does anybody have any ideas?
> Shouldn't these problems be fixed after running fsck?

That depends upon how you run the fsck.  Fsck should be run on a non-mounted
file system.  Obviously, if you are running on the system the root 
partition will be mounted, but you can run fsck with specific flags which allow
the unmounting and remounting of the root partition.  These are used in the 
/etc/bcheckrc file:

	/etc/fsck -y -s -D -b ${rootfs}

where rootfs=/dev/root.

>   ** Phase 5 - Check Free List 
>   9003 BLK(S) MISSING
>   BAD FREE LIST
>   SALVAGE? 

This will always appear under interactive (if the file system is mounted)
since they purposly damage the free list on the drive while the file
system is unmounted.  This is part of thier high performace disk driver package.

-- 
+-----------------------------------------------------------------------+
| Conor P. Cahill     uunet!virtech!cpcahil      	703-430-9247	!
| Virtual Technologies Inc.,    P. O. Box 876,   Sterling, VA 22170     |
+-----------------------------------------------------------------------+