From owner-freebsd-questions Mon Feb 24 00:07:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA07455 for questions-outgoing; Mon, 24 Feb 1997 00:07:48 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA07448 for ; Mon, 24 Feb 1997 00:07:44 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.4) id DAA00886 for freebsd-questions@freebsd.org; Mon, 24 Feb 1997 03:07:33 -0500 (EST) From: Charles Henrich Message-Id: <199702240807.DAA00886@crh.cl.msu.edu> Subject: What does async fs do in detail? To: freebsd-questions@freebsd.org Date: Mon, 24 Feb 1997 03:07:33 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am seriously considering mounting my filesystem async to get some performance increase out of my news server, currently expires are taking WAY WAY too long :(. Could someone explain what is the absolute worst scenario that can occur when a filesytem is mounted async and something bad happens (e.g. power loss on disks or server or both or whatever..) Is the disk scrambled? Or are only a handful of files lost? Thanks much guys! -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich