From owner-freebsd-current Mon Nov 17 12:21:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10897 for current-outgoing; Mon, 17 Nov 1997 12:21:15 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA10891 for ; Mon, 17 Nov 1997 12:21:03 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 4542 invoked from network); 17 Nov 1997 20:20:59 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 17 Nov 1997 20:20:59 -0000 Date: Mon, 17 Nov 1997 15:20:58 -0500 (EST) From: Evan Champion To: chuckr@glue.umd.edu cc: npp@neg-micon.dk, current@FreeBSD.ORG Subject: Re: async fs? In-Reply-To: <199711171723.MAA28442@earth.mat.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 17 Nov 1997 chuckr@glue.umd.edu wrote: > Are you aware that losing your system while you are running async is > usually fairly safe (often you lose no files, or if you were very busy > doing disk activity, maybe a few), but if you are mounted async, you > could possibly lose much, much more? It'll certainly increase > performance, but you'd better be willing to pay the price. Mounting a proxy cache or somesuch is probably a good use for async. If the disk is corrupted, the world won't end if you newfs the proxy cache. But make sure that _all_ that is on that slice is the cache. Evan