Return to BSD News archive
#! rnews 1508 bsd
Newsgroups: comp.unix.bsd.bsdi.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!chi-news.cic.net!newsfeed.internetmci.com!elvis.delphi.com!uunet!in1.uu.net!spcuna!spcvxb!terry
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Subject: Re: News HD errors
Nntp-Posting-Host: spcvxa.spc.edu
References: <45m0m3$n44@pegasus.starlink.com>
Sender: news@spcuna.spc.edu (Network News)
Organization: St. Peter's College, US
Date: Fri, 13 Oct 1995 16:11:51 GMT
Message-ID: <1995Oct13.121151.1@spcvxb.spc.edu>
Lines: 17
In article <45m0m3$n44@pegasus.starlink.com>, alschnei@starlink.com (Alan Schneider) writes:
> The daily server report was about 400K every day, with nothing but
> errors like this. I fsck'd the drive, but the same night, it reported
> the same errors.
There isn't any locking between fsck and anything else that's using the
disk. On other operating systems, the equivalent of fsck locks out all other
use accesses while it runs (for example, on DEC's VMS, ANALYZE/DISK).
What you're seeing is fsck being confused by the disk contents changing
while it's running, probably because of a news expire. You can either re-
schedule the news expire and/or nightly fsck to not conflict with each
other, or just comment the fsck out in the nightly batch job (/etc/daily).
Terry Kennedy Operations Manager, Academic Computing
terry@spcvxa.spc.edu St. Peter's College, Jersey City, NJ USA
+1 201 915 9381 (voice) +1 201 435-3662 (FAX)