From owner-freebsd-current@FreeBSD.ORG Mon Jul 21 12:48:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68C4B1065678; Mon, 21 Jul 2008 12:48:21 +0000 (UTC) (envelope-from lothar@lobraun.de) Received: from smtp.cs.uni-tuebingen.de (u-173-c156.cs.uni-tuebingen.de [134.2.173.156]) by mx1.freebsd.org (Postfix) with ESMTP id 11E2B8FC0C; Mon, 21 Jul 2008 12:48:21 +0000 (UTC) (envelope-from lothar@lobraun.de) Received: from honshu.net.informatik.tu-muenchen.de ([131.159.14.60]) by smtp.cs.uni-tuebingen.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1KKuoP-0004EU-2N; Mon, 21 Jul 2008 14:48:21 +0200 Message-ID: <48848598.1010202@lobraun.de> Date: Mon, 21 Jul 2008 14:48:24 +0200 From: Lothar Braun User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Attilio Rao References: <487F32C6.5030502@lobraun.de> <3bbf2fe10807171306y59d30b13y868c1e27697412a7@mail.gmail.com> <48805EEE.90109@lobraun.de> <48806684.4000908@FreeBSD.org> <4880921C.10700@lobraun.de> <3bbf2fe10807190827k24c738c9s4f258ac006035b75@mail.gmail.com> <48833C50.8030507@lobraun.de> <3bbf2fe10807200904y32cc6d04n94bc262aa3c6c2be@mail.gmail.com> <3bbf2fe10807200926k5aa8fd2an7b2689f92bbba05d@mail.gmail.com> <3bbf2fe10807201046i109caccfl88e8641f424226eb@mail.gmail.com> In-Reply-To: <3bbf2fe10807201046i109caccfl88e8641f424226eb@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: panic: __lockmgr_args: unknown lockmgr request 0x0 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: Mon, 21 Jul 2008 12:48:21 -0000 Attilio Rao wrote: >> > For what I remind, it is likely XFS is still not ready for writing. >> > This means you should only use it in read-only. Uh, I somehow missed it (aka didn't read xfs(5) :-(). >> >> Speaking of which, I think we should mark it again like a read-only fs >> until writing is not 100% ready. Yes, that could be a good idea. > Lothar, > can you please try this patch on the top of -CURRENT: > http://www.freebsd.com/~attilio/xfs3.diff > > it should avoid to mount an xfs partition in write mode. Yes, I'm not allowed to mount that partition in write mode, with the patch applied to the kernel. Regards, Lothar