From owner-freebsd-fs  Wed Sep 24 09:31:17 1997
Return-Path: <owner-freebsd-fs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA08607
          for fs-outgoing; Wed, 24 Sep 1997 09:31:17 -0700 (PDT)
Received: from roguetrader.com (brandon@cold.org [206.81.134.103])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08590
          for <freebsd-fs@FreeBSD.ORG>; Wed, 24 Sep 1997 09:31:08 -0700 (PDT)
Received: from localhost (brandon@localhost)
	by roguetrader.com (8.8.5/8.8.5) with SMTP id KAA05688;
	Wed, 24 Sep 1997 10:31:54 -0600 (MDT)
Date: Wed, 24 Sep 1997 10:31:54 -0600 (MDT)
From: Brandon Gillespie <brandon@roguetrader.com>
To: Terry Lambert <tlambert@primenet.com>
cc: freebsd-fs@FreeBSD.ORG
Subject: Re: Known problems with async ufs?
In-Reply-To: <199709240526.WAA02832@usr07.primenet.com>
Message-ID: <Pine.BSF.3.96.970924102942.5645A-100000@roguetrader.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-fs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 24 Sep 1997, Terry Lambert wrote:
> That answer the question?

Very much so, thanks!

Basically, with all of the down-play towards using an async FS it seemed
as if there may be bugs within the actual async code, and not just the
crash/power-fail situation problems.

I personally am running off a smart-ups, and have a daemon monitoring it
so it will shutdown properly, if need be.

-Brandon Gillespie