From owner-freebsd-fs Tue Sep 23 21:31:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA28953 for fs-outgoing; Tue, 23 Sep 1997 21:31:54 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA28928 for ; Tue, 23 Sep 1997 21:31:49 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA03571 for ; Wed, 24 Sep 1997 06:31:47 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id GAA18439 for freebsd-fs@FreeBSD.ORG; Wed, 24 Sep 1997 06:31:35 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id CAA20430; Wed, 24 Sep 1997 02:16:24 +0200 (CEST) Message-ID: <19970924021624.34229@keltia.freenix.fr> Date: Wed, 24 Sep 1997 02:16:24 +0200 From: Ollivier Robert To: freebsd-fs@FreeBSD.ORG Subject: Re: Known problems with async ufs? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Brandon Gillespie on Tue, Sep 23, 1997 at 12:11:03PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Brandon Gillespie: > UFS, which is horribly slower than async ufs. If your BOX is on a UPS, > and you are generally assured that nothing is going to cause it to simply > 'go down', why WOULDNT you want to run async on ALL filesystems? What > problems are there with it? Terry will no doubt give you many reasons why async UFS is bad (I even agree with most of them), why we should be using soft updates (which I really want to have but McKusick is still working on them I think) and/or LFS (I'd like to have it too) but my current experience for a lightly loaded machine on which I read mail and recompile CURRENT, many of my FS are async and never got a problem with them. /dev/sd0a on / (local) /dev/sd0s2e on /usr (local) /dev/sd0s2f on /usr/local (local) /dev/sd12e on /var (local) /dev/sd0s2g on /users (local) /dev/sd12f on /news (asynchronous, local, noatime, nosuid) /dev/sd0s2h on /src (asynchronous, local) (/usr/src) /dev/sd12h on /spare (asynchronous, local) (/home/ncvs) /dev/sd0s2d on /work (asynchronous, local) /dev/sd11a on /x (asynchronous, local, nosuid) /dev/sd12g on /y (asynchronous, local, noatime) (/usr/obj) procfs on /proc (local) /work/spare on /x/ftp/pub/FreeBSD/XFree86-3.3 (local, read-only) I get panics (not often even for CURRENT) and locks but still have to lose something. The risk is there, I know and accept it. Async /usr/obj helps "make world" a lot. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #35: Sun Sep 21 19:28:07 CEST 1997