Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!virtech!cpcahil From: cpcahil@virtech.UUCP (Conor P. Cahill) Newsgroups: comp.unix.questions Subject: Re: possible file size error Keywords: removal of Message-ID: <1128@virtech.UUCP> Date: 5 Sep 89 01:14:45 GMT References: <2218@netcom.UUCP> Organization: Virtual Technologies Inc Lines: 31 In article , will@presto.ig.com (Will Nelson) writes: > In article <2218@netcom.UUCP>, beaulieu@netcom.UUCP (Bob Beaulieu) writes: > > [ stuff about file size errors from fsck ] > > We used to see this many years ago on Onyx machines. > I don't remember exactly what caused it, but we did something like: > > ncheck -i 3046 filesystem > > cp offending_file offending_file.old > mv offending_file.old offending_file > > The offending_file is determined by the output of ncheck. > This got rid of the fsck complaint. Yes, this would fill in the holes in the file with nulls that any program would have gotten anyway, but you just increased the size of the file without any justification. This file size error message from fsck is just a warning. If there is a reason for the file with the hole (like a database file, or maybe an index file) then you just caused it to take up more space than it really needs to. I would recommend that you just check to ensure that the file (or the program that uses the offending_file) is supposed to have holes in it and leave it alone. It isn't bothering anybody. -- +-----------------------------------------------------------------------+ | Conor P. Cahill uunet!virtech!cpcahil 703-430-9247 ! | Virtual Technologies Inc., P. O. Box 876, Sterling, VA 22170 | +-----------------------------------------------------------------------+