Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: Regular FSCK Required ?
Keywords: why
Message-ID: <10558@dog.ee.lbl.gov>
Date: 4 Mar 91 11:26:28 GMT
References: <1235@cnw01.storesys.coles.oz.au>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 16
X-Local-Date: Mon, 4 Mar 91 03:26:28 PST

In article <1235@cnw01.storesys.coles.oz.au> nigel@cnw01.storesys.coles.oz.au
(Nigel Harwood) writes:
>Is a regular FSCK required ?

No---unless something is broken, fsck should be necessary *only* after
a power-failure crash or hardware error.  (If something *is* broken,
fix it.  If you do not have source, switch to BSD Unix.)

>Because of the low computer skill level at these sites it is a
>real battle to get any normal SA things done, like for example a
>regular FSCK of the file systems (i.e. once a week).

Do not allow fsck to change a file system that is mounted.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov