Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!noao!ncar!unmvax!uokmax!servalan!rmtodd
From: rmtodd@servalan.uucp (Richard Todd)
Newsgroups: news.software.b
Subject: Re: C news history.pag gives fsck heartburn
Message-ID: <1991Apr17.060302.23145@servalan.uucp>
Date: 17 Apr 91 06:03:02 GMT
References: <4975@lib.tmc.edu>
Organization: Ministry of Silly Walks
Lines: 19

jmaynard@thesis1.med.uth.tmc.edu (Jay Maynard) writes:
>Environment: NCR Tower XP, System Vr2 version 3.02.01.

>Running fsck on the partition with /usr/lib/news on it results in a
>"POSSIBLE FILE SIZE ERROR" complaint. Is this a bug in my fsck or in
>dbz, and is it a real problem or merely a nuisance?

 Your fsck (and, in my experience, at least one other SVR2 fsck) is being 
confused by the fact that dbz files are "holey", i.e. they contain blocks in 
the middle that have never been written to.  The fsck is presumably comparing
the listed size in the inode to the number of blocks allocated to that inode
and finding a "possible file size error".  It isn't a problem at all; as I
recall, fsck doesn't actually *do* anything to the file, just note a possible
error.  It's just a minor nuisance; learn to expect one POSSIBLE FILE SIZE
ERROR complaint per dbm file.  Don't worry about it.  
--
Richard Todd	rmtodd@uokmax.ecn.uoknor.edu  rmtodd@chinet.chi.il.us
	rmtodd@servalan.uucp
"Elvis has left Bettendorf!"