From owner-freebsd-current Thu May 14 04:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03706 for freebsd-current-outgoing; Thu, 14 May 1998 04:08:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03587 for ; Thu, 14 May 1998 04:07:55 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id TAA16215; Thu, 14 May 1998 19:06:46 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805141106.TAA16215@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Hancock cc: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: soft updates and async In-reply-to: Your message of "Thu, 14 May 1998 17:25:15 +0900." Date: Thu, 14 May 1998 19:06:45 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Hancock wrote: > On Thu, 14 May 1998, Mikhail Teterin wrote: [..] > > Will I be able to combine async and softupdates in the future and why > > would I want to? > > No, they are mutually exclusive. If you do a write it is either sync > (default), async, or delayed (softupdates). You'd have no reason to > combine them unless you want to get undefined behavior. In this case, undefined == panic.. The softupdate code gets *very* upset when certain sync writes are not performed when expected. The -o async code interferes with those. At least, that's the way it was a few months ago when I forgot to remove an async mount option from my fstab after enabling softupdates in single user. > Regards, > > Mike Hancock Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message