Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!labrea!aurora!ames!hao!noao!arizona!whm
From: whm@arizona.edu (Bill Mitchell)
Newsgroups: comp.unix.wizards
Subject: Re: bad bitmaps that fsck can't seem to fix (4.3+NFS from Mt. Xinu)
Message-ID: <1828@megaron.arizona.edu>
Date: Thu, 23-Jul-87 18:32:24 EDT
Article-I.D.: megaron.1828
Posted: Thu Jul 23 18:32:24 1987
Date-Received: Sat, 25-Jul-87 12:19:29 EDT
References: <1825@megaron.arizona.edu>
Organization: U of Arizona CS Dept, Tucson
Lines: 18

In article <1825@megaron.arizona.edu> I wrote:
> One of our 785s running 4.3+NFS has a couple of filesystems that when checked,
> produce the message "BLK(S) MISSING IN BIT MAPS". fsck claims to "salvage"
> the bit maps, but a subsequent run of fsck produces the same diagnostic.
> 
> Running icheck on these filesystems produces several messages of the form:
> 
>  dup frag; inode=0, class=free frag
>
> ...

We noticed that while running fsck we'd frequently get a soft ecc on one of
the memory controllers.  We took out that controller and now fsck and icheck
pronounce those filesystems as being ok. (!)

					Bill Mitchell
					whm@arizona.edu
					{allegra,cmcl2,ihnp4,noao}!arizona!whm