Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!chi-news.cic.net!newsfeed.internetmci.com!in1.uu.net!news.starlink.com!usenet From: alschnei@starlink.com (Alan Schneider) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: BSDI v2.0.1 with distribution innd -> filesytem problems in daily report Date: Mon, 13 Nov 1995 04:30:09 GMT Organization: StarLink Internet Services Lines: 24 Message-ID: <486h2r$krq@pegasus.starlink.com> References: <47tgl7$e48@news.atlantech.net> NNTP-Posting-Host: alschnei.starlink.com X-Newsreader: Forte Free Agent 1.0.82 ramoore@atlantech.net (Randy Moore) wrote: >I am running the INN version that comes with BSDI v2.0.1 >(does anyone know for sure the version number of innd?) and >the daily report created by /etc/daily shows many file system >errors (daily reports run about 100 kbytes). If I dismount >these files systems and manually run fsck, it shows no >problems. >My solution has been to disable the daily run of fsck. >Has anyone else had this "problem" and what possible problems >am I causing by not running fsck nightly? I have had the EXACT same problem. I arranged the expire and daily crons to run at such times as they do not overlap. This overlap is what causes the problem. Even with rearrange, I still catch the tail end of expire. I'll probably trash the daily and manually run fsck periodically. >Thanks for any info or suggestions. >- Randy Moore