Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!ucbvax!unisoft!asa
From: asa@unisoft.UUCP (Asa Romberger)
Newsgroups: comp.unix.wizards
Subject: Re: creeping fsck bug with System V FIFO
Message-ID: <1349@unisoft.UUCP>
Date: 26 Oct 88 16:06:05 GMT
References: <6607@venera.isi.edu>
Reply-To: asa@noir.UUCP (Asa Romberger)
Organization: UniSoft Corporation, Emeryville Ca.
Lines: 16

In article <6607@venera.isi.edu> cracraft@venera.isi.edu (Stuart Cracraft) writes:
>I have a System V machine; When I do an fsck, it reports
>Possible file size error, and then "I=nnnn" where the
>inode is named.
>
>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.

1/ /usr/spool/lp/FIFO is created by lp when it runs, if it does not already
   exist. It is a named pipe.
2/ Some versions of fsck for System V do not handle named pipes correctly and
   frequently list them as "Possible file size error".