From owner-freebsd-current@FreeBSD.ORG Thu Sep 29 21:13:26 2005 Return-Path: X-Original-To: freebsd-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 075DE16A41F; Thu, 29 Sep 2005 21:13:26 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1BE143D4C; Thu, 29 Sep 2005 21:13:25 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 4E96346B14; Thu, 29 Sep 2005 17:13:25 -0400 (EDT) Date: Thu, 29 Sep 2005 22:13:25 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael Nottebrock In-Reply-To: <200509292031.01164.lofi@freebsd.org> Message-ID: <20050929221041.H34322@fledge.watson.org> References: <200509220113.06667.lofi@freebsd.org> <200509220135.56826.lofi@freebsd.org> <200509292031.01164.lofi@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: UFS_EXTATTR(_AUTOSTART) broken on 6.0-BETA5 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: Thu, 29 Sep 2005 21:13:26 -0000 On Thu, 29 Sep 2005, Michael Nottebrock wrote: > On Thursday, 22. September 2005 01:35, Michael Nottebrock wrote: >> On Thursday, 22. September 2005 01:13, Michael Nottebrock wrote: >>> [...] >>> ad0: 76351MB at ata0-master UDMA100 >>> acd0: DVDROM at >>> ata1-master UDM >>> A33 >>> Trying to mount root from ufs:/dev/ad0s1a >>> panic: lockmgr: unknown locktype request 0 > > Has anyone had time to look into this yet? It would be really nice if > could keep using ACLs on this machine, but I do not have the means to > make a full backup and convert the filesystems to UFS2 (where I suppose > this problem doesn't exist). I know that Christian has been looking into this. My initial reading based on a quick skim was that the life cycle of early vnodes in file system mount had changed as a result of the VFS locking work, but Christian has indicated to me that the bug isn't reproduceable 100% of boots for him, and that Jeff felt this might reflect a race. Does this panic occur for you every boot? If you set debug.mpsavevfs=0 in loader.conf, does that make any difference? I may have the opportunity to work on this this weekend, but not entirely clear. If Christian is already running with it, I'd much rather let him take this one on as I have a lot of other things on my plate. Robert N M Watson