Received: from dolphin by minnie.cs.adfa.oz.au (8.6.8/8.3) with SMTP id PAA18811; Thu, 7 Dec 1995 15:07:46 +1059
Received: by dolphin (5.x/SMI-SVR4)
	id AA12021; Thu, 7 Dec 1995 15:07:59 +1100
From: wkt@dolphin.cs.adfa.oz.au (Warren Toomey)
Message-Id: <9512070407.AA12021@dolphin>
Subject: Fsck tips
To: oldunix@minnie.cs.adfa.oz.au
Date: Thu, 7 Dec 1995 15:07:59 +1100 (EST)
In-Reply-To: <199512070347.TAA02505@wlv.iipo.gtegsc.com> from "Steven M. Schultz" at Dec 6, 95 07:47:48 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text

In atricle by Steven M. Schultz:
> > I have dchecked, ichecked and fscked /dev/ra0f, and it seems to
> > be a happy partition.
> 
> 	Ok - at that point if a manual "fsck /dev/rra0f" (and you should be
> 	using the raw (rra) form of the device) works, then all you need to
> 	do is hit a ^D and the system will finish coming up to a multi user
> 	state.

Apropos fsck'ing, always work on a raw device. Only fsck on an unmounted
partition, or a quiescent one (no disk activity, this means single-user mode
and sync BEFORE doing the fsck). If fsck finds an error, DONT sync the system
before shutting down; sync will flush out anything still in the cache, possibly
overwriting the changes fsck made to the disk.

Someone had to point this out to me a few years ago, I kept doing
sync sync sync reboot after fsck reported errors. Deary me!

Cheers all,
	Warren

