From owner-freebsd-current@FreeBSD.ORG Tue May 23 15:40:15 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E89B516A595 for ; Tue, 23 May 2006 15:40:15 +0000 (UTC) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6CFE43D82 for ; Tue, 23 May 2006 15:39:53 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.171.127.191] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1FiYzA-000PNt-1w; Tue, 23 May 2006 09:39:52 -0600 In-Reply-To: <20060523173118.371a283e@Magellan.Leidinger.net> References: <20060522211223.GA3621@xor.obsecurity.org> <20060522231437.GC1446@odin.ac.hmc.edu> <20060523133037.GA2908@gothmog.pc> <20060523143013.GA11472@ci0.org> <20060523141757.GA2966@gothmog.pc> <20060523173118.371a283e@Magellan.Leidinger.net> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <359223C4-42CF-4652-BC1F-892BCBE668D4@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Tue, 23 May 2006 09:39:50 -0600 To: Alexander Leidinger X-Mailer: Apple Mail (2.750) X-SA-Exim-Connect-IP: 67.171.127.191 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: Giorgos Keramidas , current@freebsd.org, Kris Kennaway Subject: Re: md /tmp and async mounts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 15:40:17 -0000 On May 23, 2006, at 9:31 AM, Alexander Leidinger wrote: > Quoting Giorgos Keramidas (Tue, 23 May > 2006 17:17:57 +0300): > >>> >>> The sys/dev/md/md.c rev 1.115 commit log says async used to be >>> the default, but was switched off because it was causing >>> deadlocks. Did this get fixed since ? >> >> I am not sure. If a deadlock *does* exist though, then it's not >> an improvement and we should definitely keep the default to its >> current state until the bug is fixed. > > AFAIK it isn't. Therefore we have > http://www.freebsd.org/projects/ideas/index.html#p-mdfs > I've been having a problem since 5.3 days (currently on 6.0-RELEASE some p level) that happens very infrequently (every couple of weeks to every couple of months) that looks to be the same thing. I am not creating my md devices using option async. In reading the CVS log for rev 1.115 it seems that async was turned off as the default to avoid this problem, and that if I am suffering from the same problem, I shouldn't be as sync is the default now on md creation. Am I reading this correctly? Thanks Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net