I tried:

# umount /var/spool/news
umount: /var/spool/news: Device busy

# newfs /dev/rccd0d
newfs: /dev/rccd0d: Device busy

how do I unbz this thing so I can try newfs-ing it to see if it's bad?

On Tue, 17 Jun 1997, Mike Long wrote:

> >Date: Tue, 17 Jun 1997 00:47:24 -0500 (CDT)
> >From: "Tom T. Thai" <tomthai@future.net>
> >
> ># fsck_ffs /var/spool/news
> >** /dev/rccd0d (NO WRITE)
> >
> >CANNOT READ: BLK 16
> >CONTINUE? [yn] y
> >
> >THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21, 22, 
> >23, 24, 25, 2
> >6, 27, 28, 29, 30, 31,
> >Floating point exception - core dumped
> 
> I think I've seen this one before; it's probably a divide-by-zero
> error.  I don't remember how I fixed it, sorry.
> 
> I would say that if that many sectors couldn't be read, then it's time
> for newfs and possibly disk replacement.
> -- 
> Mike Long <mikel@shore.net>                http://www.shore.net/~mikel
> "Every normal man must be tempted at times to spit on his hands,
> hoist the black flag, and begin slitting throats." -- H.L. Mencken
> 


..............          ....................................
Thomas T. Thai          Infomedia Interactive Communications
tom@iic.net             TEL 612.376.9090 * FAX 612.376.9087