Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!cs.utexas.edu!swrinde!gatech!news-feed-1.peachnet.edu!insosf1.infonet.net!s069.infonet.net!cynjut.infonet.net!not-for-mail
From: burgess@cynjut.infonet.net (Dave Burgess)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FBSD-1.1.5.1: filesystem problems ?
Date: 4 Dec 1994 11:07:14 -0600
Organization: Configuration Management Svcs, Inc.
Lines: 39
Message-ID: <3bst02$6do@cynjut.infonet.net>
References: <Czzw5p.GI9@luva.lb.bawue.de>
NNTP-Posting-Host: cynjut.infonet.net
In article <Czzw5p.GI9@luva.lb.bawue.de>,
Michael Giegerich <migieger@luva.lb.bawue.de> wrote:
>
>After upgrading from FBSD-1.0.2 to FBSD-1.1.5.1 (with all patches
>"blessed" by Rod) I find at least every 2nd or 3rd day complaints
>from fsck in my logs of the /etc/daily scripts.
>
>Very anoying! Most times only some files from the /usr/spool/news
>tree are concerned but I had already to come back to my backups
>(a praise to DAT streamers :-).
>
>Has anybody else experienced this behaviour? Any solutions to
>known problems?
>
>And no, it's not my hard disk (the grown defect list is still 0).
>
I was seeing behaviour like this once upon a time when my downstream
news service would send me news batches at the same time my daily
started.
I would get unreferenced files and other 'apparent' system problems
during the news updates. I assumed that these problems were related to
the fact that innd was unbatching and processing news articles during
the fsck. When I changed my daily run so that it ran at a quieter time
of day, it ran without complaint.
Are all file system updates supposed to the completely atomic? I, for
one, would expect a few of these laying around during processing,
especially something as inode invasive as news updates seem to be.
--
TSgt Dave Burgess | Dave Burgess
NCOIC, USSTRATCOM/J6844 | *BSD FAQ Maintainer
Offutt AFB, NE | Burgess@cynjut.infonet.net or ...@s069.infonet...