It doesn't neccessarily mean the fs is corrupt - it may just be
	'in the process' of updating the disk.

	The fsck really needs to be run after the disk has been
	synchronised, which is kinda difficult to do on an active
	system :)

		David/abs	david@{mono.org,southern.com,mhm-internet.com}

Thought for : Loathing the way "Don't cry for me Argentina" has
  the day   : been bastardized by Madonna into a 'disco' song.

On Wed, 5 Feb 1997, Peter Berg wrote:

> > 
> > A question for you guru's out there.
> > 
> > I am now able to run RiscBSD continuously, and have been for the last 
> > 3 weeks or so (with the odd reboot while i play with things) while i 
> > have a small news service going here.  BEcause of this the daily and 
> > week cron tabs are able to run, but the daily one keeps producing 
> > this:
> > -------------------------------------------------------------------
> > Checking filesystems:
> > ** /dev/rwd0a (NO WRITE)
> > ** Last Mounted on /
> > ** Root file system
> > UNREF FILE I=4010  OWNER=root MODE=100644
> > SIZE=0 MTIME=Jan 29 02:00 1997 
> > CLEAR? no
> > 
> > 929 files, 14732 used, 14467 free (115 frags, 1794 blocks, 0.4% fragmentation)
> > ** /dev/rwd0e (NO WRITE)
> > ** Last Mounted on /usr
> > INCORRECT BLOCK COUNT I=74965 (2 should be 0)
> > CORRECT? no
> > 
> > LINK COUNT FILE I=15365  OWNER=news MODE=0
> > SIZE=0 MTIME=Jan 29 02:00 1997  COUNT 0 SHOULD BE -1
> > ADJUST? no
> > 
> > UNREF FILE I=74965  OWNER=news MODE=0
> > SIZE=0 MTIME=Jan 29 02:00 1997 
> > CLEAR? no
> > 
> > FREE BLK COUNT(S) WRONG IN SUPERBLK
> > SALVAGE? no
> > 
> > BLK(S) MISSING IN BIT MAPS
> > SALVAGE? no
> > 
> > SUMMARY INFORMATION BAD
> > SALVAGE? no
> > 
> > 6871 files, 194461 used, 149075 free (2755 frags, 18290 blocks, 0.8% fragmentation)
> 
> This means you have a corrupt filesystem, to do nothing will be very dangerous 
> !
> Because of some unknown reason the ffs has been marked clean when it wasn't 
> clean, and therefore the ffs isn't checked when you boot and reported as clean.
> 
> Try to boot in single user mode and then run fsck manually on each partition
> 
> 	fsck /dev/wd0a
> 	fsck /dev/wd0e
> 
> This should fix the ffs.
> 
> 	Ciao, peter
> 
>