Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: creeping fsck bug with System V FIFO Message-ID: <12865@ncoast.UUCP> Date: 2 Nov 88 17:50:01 GMT References: <6607@venera.isi.edu> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.unix.wizards Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 28 As quoted from <6607@venera.isi.edu> by cracraft@venera.isi.edu (Stuart Cracraft): +--------------- | When inspected with ncheck, this inode turns out to be | that for /usr/spool/lp/FIFO. If I delete this file and | then run fsck again, I figured it would clean things up. | A half hour later I discovered FIFO was back again and | fsck was getting the same error again. +--------------- The only bug here is that fsck doesn't quite know what to do with a FIFO. /usr/spool/lp/FIFO is part of the spooler system, and is quite normal aside from fsck's slight brain damage. However, removing it while the spooler is running is a good way to f*ck up the spooler. Recommended treatment: none. Ignore the error (my experience is that if the POSSIBLE FILE SIZE ERROR isn't matched by a later error for the same inode, it's just a piece of fsck braindamage that can be ignored). Maybe complain to whoever ported the UNIX; I've seen System V fsck's which understand FIFOs and files with holes in them. ++Brandon -- Brandon S. Allbery, comp.sources.misc moderator and one admin of ncoast PA UN*X uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu allberyb@skybridge.sdi.cwru.edu allbery@uunet.uu.net comp.sources.misc is moving off ncoast -- please do NOT send submissions direct Send comp.sources.misc submissions to comp-sources-misc@.