creeping fsck bug with System V FIFO

[Asa Romberger]

In article <6607 at venera.isi.edu> cracraft at 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".