Path: utzoo!attcan!uunet!unisoft!bdt!wm6r!jjt
From: jjt@wm6r.UUCP (John Thornton)
Newsgroups: comp.unix.microport
Subject: BAD FREE LIST in Microport SV/AT 2.3U
Message-ID: <514@wm6r.UUCP>
Date: 25 Nov 89 05:57:21 GMT
Organization: wm6r in Berkeley, CA
Lines: 30

The file system used here for /usr/spool/news has become corrupted about
every 6 months, an fsck gives:

  /dev/dsk/1s1
  File System:  Volume: 

  ** Phase 1 - Check Blocks and Sizes
  ** Phase 2 - Check Pathnames
  ** Phase 3 - Check Connectivity
  ** Phase 4 - Check Reference Counts
  ** Phase 5 - Check Free List 
  -3022 BLK(S) MISSING
  BAD FREE LIST
  SALVAGE? y

  ** Phase 6 - Salvage Free List
  5423 files 33234 blocks 13358 free
  *** FILE SYSTEM WAS MODIFIED ***

Unfortunately, fsck isn't able to fix the file system and I end up
remaking the file system and restoring from backups.  I am at a loss as to
why fsck shows a large negative number of blocks missing.  The file system
is unmounted during this operation.  Successive fscks give the same message.

Anyone know of a work around for this?


-- 
John Thornton 				P.O. Box 59 Berkeley, CA 94701
{ucbvax,uunet}!unisoft!wm6r!jjt		unisoft!wm6r!jjt@ucbvax.berkeley.edu