From owner-freebsd-current Wed May 13 20:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23473 for freebsd-current-outgoing; Wed, 13 May 1998 20:31:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23467; Wed, 13 May 1998 20:31:12 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA16124; Wed, 13 May 1998 20:30:53 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd016119; Thu May 14 03:30:44 1998 Date: Wed, 13 May 1998 20:30:41 -0700 (PDT) From: Julian Elischer To: Kris Kennaway cc: "Jordan K. Hubbard" , julian@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Crash with latest soft updates and SMP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG no it's not documented and yes it should be :-) (I will try add a patch to make it irrelevent) On Thu, 14 May 1998, Kris Kennaway wrote: > On Wed, 13 May 1998, Julian Elischer wrote: > > > I guess ufs should unset the async bit if softupdates is set.... > > Aha! I was going to spend some more time tonight tracking down the cause > of the panics I experienced after testing this last night. However, after > reading this it's probably caused by mounting async. > > Was I just being blind and dense, or is this not actually documented > anywhere obvious? > > Kris > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message