From owner-freebsd-current@FreeBSD.ORG Sun Feb 8 12:05:16 2009 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 80E81106568C; Sun, 8 Feb 2009 12:05:16 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate02.web.de (fmmailgate02.web.de [217.72.192.227]) by mx1.freebsd.org (Postfix) with ESMTP id 10AF28FC1B; Sun, 8 Feb 2009 12:05:15 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate02.web.de (Postfix) with ESMTP id 9428FFA21BBC; Sun, 8 Feb 2009 13:05:14 +0100 (CET) Received: from [217.236.42.73] (helo=zelda.local) by smtp06.web.de with asmtp (TLSv1:AES128-SHA:128) (WEB.DE 4.110 #277) id 1LW8PS-0001PE-00; Sun, 08 Feb 2009 13:05:14 +0100 Date: Sun, 8 Feb 2009 13:05:06 +0100 From: Martin To: Kris Kennaway Message-ID: <20090208130506.267a838d@zelda.local> In-Reply-To: <498EB79F.4010905@FreeBSD.org> References: <1233007263.9302.2.camel@localhost.localdomain> <20090129233220.1ed64e6d@zelda.local> <498EB79F.4010905@FreeBSD.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX18SdexEwhmqZBTVK30+Izr2urN56RbNo77lNxI9 4D9MJp8lo5VDvo48JfuPAb35WFH6/IcNWM9zyflBPPU18JNZh/ yTJVDMyyQ= Cc: sean.bruno@dsl-only.net, sbruno@freebsd.org, freebsd-current@freebsd.org Subject: Re: UFS Witness LoR + 5 other LoRs 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: Sun, 08 Feb 2009 12:05:17 -0000 Am Sun, 08 Feb 2009 11:44:47 +0100 schrieb Kris Kennaway : > Several of these are widely reported, and harmless (not sure about > the filedesc ones though). Which one do you think is causing your > problem? > > Kris Hi Kris. I found out it has something to do with the softlink to an NFS share that I have on my desktop (nautilus). I've made some settings yesterday to fix it and will report, if this was the problem. Of course, the amd mounts and unmounts my NFS share and the mentioned LORs appear typically while mounting and unmounting, I noticed. So it is perhaps misleading. Btw... it would be very nice if someone finally implements timeouts and a detection strategy for NFS packets that don't arrive at their destination because of fragmentation and wrong rsize/wsize settings. But this is a totally different topic. There is not much in the docs about it. You mean this LOR "with filedesc"? lock order reversal: 1st 0xffffff001ada0ba8 zfs (zfs) @ /usr/src/sys/kern/vfs_subr.c:2071 2nd 0xffffff0008a92848 filedesc structure (filedesc structure) @ /usr/src/sys/kern/vfs_syscalls.c:1720 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_slock() at _sx_slock+0x55 kern_symlinkat() at kern_symlinkat+0x1f8 syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (57, FreeBSD ELF64, symlink), rip = 0x8049cc13c, rsp = 0x7fffffffd6f8, rbp = 0x7fffffffdd10 --- It still occurs on: FreeBSD zelda.local 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Feb 2 19:20:24 CET 2009 root@zelda.local:/usr/obj/usr/src/sys/ZELDA amd64 It appears a bit later when Gnome is already running, I think. I can only tell by looking at the time stamp that is 3 minutes after booting the machine. I'll to try to figure out what is running when exactly this LOR appears. -- Martin