From owner-freebsd-questions@FreeBSD.ORG Thu Aug 23 11:04:46 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9382816A41B for ; Thu, 23 Aug 2007 11:04:46 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC4413C467 for ; Thu, 23 Aug 2007 11:04:46 +0000 (UTC) (envelope-from me@janh.de) Received: from d054074.adsl.hansenet.de [80.171.54.74] (helo=janh.freebsd) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1IOAUW2XEB-0006vs; Thu, 23 Aug 2007 13:04:45 +0200 Message-ID: <46CD69D1.2040009@janh.de> Date: Thu, 23 Aug 2007 13:04:49 +0200 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: questions-list freebsd References: <46CD5268.3010704@janh.de> In-Reply-To: <46CD5268.3010704@janh.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/h2TMYJNgV+leJtDPIIVpYlsYBBDeW1dohuaO hG8iIFzZKTKSXatsjjVDorhT35oUPHovWCg5/oQ1npyo9X7/Ii U+iJUhJHImtPWoVYGIMBA== Cc: rodrigc@FreeBSD.org Subject: Re: Reproducible panic of 6.2 on double mount ntfs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2007 11:04:46 -0000 Jan Henrik Sylvester wrote: > With '/dev/ad0s1 /mnt/ad0s1 ntfs ro,noauto 0 0' in fstab, if I issue > 'mount /mnt/ad0s1' twice, I always get a panic with the message: > > panic: lockmgr: locking against myself I should have done some more intelligent research before... kern/89966 (6.0-STABLE) is exactly what I see. (The difference between my mount+fstab and manual mount_ntfs is that the first includes ro.) kern/104393 (7.0-CURRENT) does not even have the ro, but is otherwise the same. kern/71391 (5.2.1-RELEASE) might be related... I wonder why a panic that seems to be so easy to reproduce is not analyzed and fixed -- probably ntfs is simply not very important to anyone and the panic can be avoided quite easily. Since I should be able to avoid issuing repeated execution of mount with some concentration (I ran into this four times now), it should not be too much of an issue for me, either... Regards, Jan Henrik