From owner-freebsd-hackers Mon Mar 10 14:24:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA02763 for hackers-outgoing; Mon, 10 Mar 1997 14:24:39 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA02758 for ; Mon, 10 Mar 1997 14:24:30 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA23669; Mon, 10 Mar 1997 15:15:14 -0700 From: Terry Lambert Message-Id: <199703102215.PAA23669@phaeton.artisoft.com> Subject: Re: freebsd as a news server? To: scrappy@hub.org (The Hermit Hacker) Date: Mon, 10 Mar 1997 15:15:14 -0700 (MST) Cc: marc@bowtie.nl, neal@pernet.net, hackers@FreeBSD.ORG In-Reply-To: from "The Hermit Hacker" at Mar 10, 97 12:42:29 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Just wondering: > > > > Has anyone using the async option ever had to restore their > > filesystem? I'm seeing a lot of warnings about using it, but > > I'm wondering about actual experience figures. > > > No, have been lucky so far...am running both noatime and async > on my spool, and run it 24/7 without a problem, and do have panic > reboots occasionally... > > I don't know if running fsck -y instead of fsck -p helps that > though, in the rc file... Are you rebuilding the index file each time you crash? If not, you may end up with "stale" index entries for articles which no longer exist on your machine, either becuse they were being written at the time of the crash, or because the crash caused their directory entries to disappear, or because the index was being updated at the time of the failure. This isn't a big deal, but it is a potential problem that would not be obvious following a successful completion of a fsck, which only picks *a* consistent state to restore to, not *the* consistent state. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.