Subject: Re: Help with root file system corruption
To: None <>
From: Duncan McEwan <duncan@Comp.VUW.AC.NZ>
List: current-users
Date: 05/11/1994 10:39:06
Scott B. Anderson said:
> I'm running -current as of 2 days ago,  and I get get a 
> link count 14 should be 13; correct (y/n) ?  
> You know the matter how many times I tell it
> to fix it, or clear the 2 unreferenced files after it,
> it does nothing so far as I can tell.

To which Chris G. Demetriou replied:
> if it's your root file system, you should probably 'reboot -n'

I sent Scott the same suggestion in private mail, but then afterwards
decided to check whether I was correct (I know that 'reboot -n' used to be
necessary with older unices such as 7th edition, but back then fsck explicity
printed out "REBOOT UNIX (NO SYNC)", which is no longer the case).

On looking at the fsck sources, it seems that "fsck" will always exit with
status 4 if it has to fix a mounted root file system.  If fsck was running with
'-p' from /etc/rc, this will cause a "reboot" rather than "reboot -n".

So, is it no longer necessary to do the reboot with no sync in the event of
fixing a mounted root, or is it just not needed when using the '-p' option,
perhaps because of the limited range of errors that '-p' is able to correct?