From owner-freebsd-current@FreeBSD.ORG Tue May 8 01:14:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 002D7106564A; Tue, 8 May 2012 01:14:19 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 7C25D150929; Tue, 8 May 2012 01:14:19 +0000 (UTC) Message-ID: <4FA8736B.1040300@FreeBSD.org> Date: Mon, 07 May 2012 18:14:19 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/12.0.1 MIME-Version: 1.0 To: Mateusz Guzik References: <4FA6F324.4080107@FreeBSD.org> <4FA82269.6080406@FreeBSD.org> <20120507201153.GA19942@dft-labs.eu> In-Reply-To: <20120507201153.GA19942@dft-labs.eu> X-Enigmail-Version: 1.5pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: mckusick@freebsd.org, Sergey Kandaurov , freebsd-current Subject: Re: panic, seems related to r234386 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, 08 May 2012 01:14:20 -0000 On 05/07/2012 13:11, Mateusz Guzik wrote: > On Mon, May 07, 2012 at 12:28:41PM -0700, Doug Barton wrote: >> On 05/06/2012 15:19, Sergey Kandaurov wrote: >>> On 7 May 2012 01:54, Doug Barton wrote: >>>> I got this with today's current, previous (working) kernel is r232719. >>>> >>>> panic: _mtx_lock_sleep: recursed on non-recursive mutex struct mount mtx >>>> @ /frontier/svn/head/sys/kern/vfs_subr.c:4595 >> >> ... >> >>> Please try this patch. Ok, so far so good. Again, thanks for the quick response. I'm stress-testing my ext2fs partitions a bit atm, and everything seems Ok. I'll let you know if I run into any problems. So my next question is, does removing those locks present any risks? Should they be replaced by different locks, or were they just safety belts to start with? Finally, should my next step be to advance to the latest current + your patch and see how I go from there? Doug -- This .signature sanitized for your protection