From owner-freebsd-hackers Tue Jun 9 06:35:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21754 for freebsd-hackers-outgoing; Tue, 9 Jun 1998 06:35:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21725 for ; Tue, 9 Jun 1998 06:34:58 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id PAA29903; Tue, 9 Jun 1998 15:34:40 +0200 (MET DST) Date: Tue, 9 Jun 1998 15:28:47 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Lorenzo.Cavassa@ALPcom.IT cc: FreeBSD hackers mailing list Subject: Re: Newbie 3 questions. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : ... and (as John well knows) it can be tuned to run an async policy > : similar to the one in Linux. Which policy you run is a tradeoff > > how? mount -o async or while the system is running mount -o update,async Example rm -rf /usr (coule of thousand files) Takes minutes. mount -o update,async /usr ; rm -rf /usr ; mount -o update,sync /usr Takes 2 seconds on a pentiumII and 13 seconds on a P233 (SDRAM, both cases) Try it! And see for yourself! BIG GRIN :-]]] If you have anything operational, DON'T USE ASYNC! You'll have 0 byte files before you know it after a crash/unexpected reboot. And believe me, you're going to search all over the place to find that one. Be warned. Nick STA-ISIS, T.P.270, Joint Research Centre, Italy building: 27A tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message