From owner-freebsd-questions@FreeBSD.ORG Fri Mar 10 01:48:09 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58B7F16A420 for ; Fri, 10 Mar 2006 01:48:09 +0000 (GMT) (envelope-from jahilliya@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2F8A43D49 for ; Fri, 10 Mar 2006 01:48:08 +0000 (GMT) (envelope-from jahilliya@gmail.com) Received: by wproxy.gmail.com with SMTP id i32so548014wra for ; Thu, 09 Mar 2006 17:48:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Ycu65wMElnGA2JLP4JOJS1JQcuYafVbaD6i954UX+A8Ghp07bE3dh+VGbdRJ+KaPqS3ukfzBn1oCx4WkLVLNitEreYqlQVCYA9ebRX5oE1bg9cXw/M/xFNleyv2PZKT7WHKW8xNLE2Yfdfm0ypsqLZl+Tc4fQQQXaMZM1A6ILbk= Received: by 10.64.181.19 with SMTP id d19mr237590qbf; Thu, 09 Mar 2006 17:48:08 -0800 (PST) Received: by 10.64.180.6 with HTTP; Thu, 9 Mar 2006 17:48:08 -0800 (PST) Message-ID: Date: Fri, 10 Mar 2006 09:48:08 +0800 From: Jahilliya To: "Kris Kennaway" In-Reply-To: <20060310014140.GA681@xor.obsecurity.org> MIME-Version: 1.0 References: <20060310014140.GA681@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: System Panic 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: Fri, 10 Mar 2006 01:48:09 -0000 On 3/10/06, Kris Kennaway wrote: > > On Fri, Mar 10, 2006 at 08:38:35AM +0800, Jahilliya wrote: > > Hey, > > > > Got this error on FreeBSD 6.0-RELEASE-p5 > > > > panic: lockmgr: locking against myself > > Try updating to 6.1, many of these panics have been fixed. It's going to be for a production server and 6.1 is still under development so I'd rather not at this time I did however find out what caused the panic, it was my friend unionfs. I had a unionfs mount setup for the system distfiles to mount over the distfiles directory in one of my ports. I did a simple test: mount_unionfs /tmp/dir1 /tmp/dir2 touch /tmp/dir2/file mv /tmp/dir2/file /tmp/dir2/file1 The system immediately panicked with the exact same error... I'll move on up to 6.1 when it's stable :)