From owner-freebsd-questions Tue Oct 22 21:41:56 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA05116 for questions-outgoing; Tue, 22 Oct 1996 21:41:56 -0700 (PDT) Received: from io.org (io.org [198.133.36.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA05108 for ; Tue, 22 Oct 1996 21:41:49 -0700 (PDT) Received: from zot.io.org (root@zot.io.org [198.133.36.82]) by io.org (8.6.12/8.6.12) with ESMTP id AAA00598 for ; Wed, 23 Oct 1996 00:41:44 -0400 Received: (from batsy@localhost) by zot.io.org (8.7.5/8.7.3) id AAA25441; Wed, 23 Oct 1996 00:41:43 -0400 (EDT) Date: Wed, 23 Oct 1996 00:41:41 -0400 (EDT) From: jamie To: freebsd-questions@freebsd.org Subject: mount -o -async Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In the mount man page the async option is said to be very dangerous.=20 I watched someone time a tar -xvf and when the filesystem was mounted=20 asynchronously it was about 10x faster. This kind of speed is really=20 really tempting but I'm wondering if anyone has any stats on how likely=20 it is that I'll lose my filesystem(s) when it crashes. Is it garunteed or= =20 will I just lose anything that wasn't synched to disk before the=20 crash.(40 sec worth of data) I'm using a Quantum Fireball 1.08G EIDE drive. No, I have no intention of using this on a production machine:) If I'm not sure what I'm talking about please don't hesitate to point it=20 out:)=20 -j "Information wants to be $4.95" --erikb J=E4mie Reid Jr Systems Administrator io.org/ican.net b=E4tsy@io.org/ican.n= et