Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.hawaii.edu!ames!hookup!news.mathworks.com!news.kei.com!nntp.coast.net!howland.reston.ans.net!sol.ctr.columbia.edu!proto.ida.org!news From: ganderso@ida.org Newsgroups: comp.unix.bsd.freebsd.misc Subject: fsck question Date: 6 Feb 1996 14:05:04 GMT Organization: IDA, Alexandria, Virginia Lines: 16 Message-ID: <4f7n6g$221@dmsoproto.ida.org> Reply-To: ganderso@ida.org NNTP-Posting-Host: ganderson-pc.oed.ida.org X-Newsreader: IBM NewsReader/2 v1.2 My apologies if this has been covered elsewhere. I have a FreeBSD 2.1.0R system that has an unref file error. Running fsck finds this and I tell it to go ahead and fix it. It says that it's fixed, but if I run fsck again later, it finds the same unref file. The file in question is on the root partition, and I believe that its in the /var/log directory, but I'm not sure. Since I am not a Un*x (or FreeBSD) guru, could someone tell me how to actually fix this problem. The system seems to run fine, but this error is annoying. In case it matters, the system specifics are: 100 MHz AMD 486 with 16 Mb RAM, Adaptec 1542B SCSI Host Adapter, 1 Gb Micropolis drive, and an Acton NIC (which is being used in NE2000 compatible mode). Thanks, -Andy