From owner-freebsd-current Fri Feb 13 21:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01970 for freebsd-current-outgoing; Fri, 13 Feb 1998 21:45:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01964 for ; Fri, 13 Feb 1998 21:45:01 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id WAA20962 for ; Fri, 13 Feb 1998 22:34:17 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd020955; Fri Feb 13 22:34:10 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id WAA25250 for current@freebsd.org; Fri, 13 Feb 1998 22:34:10 -0700 (MST) From: Terry Lambert Message-Id: <199802140534.WAA25250@usr01.primenet.com> Subject: NFS locking patches -- status update To: current@FreeBSD.ORG Date: Sat, 14 Feb 1998 05:34:10 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I've received one bug report on the NFS locking patches. If anyone else is playing with them, here's how you should send me debug information: 1) Do a truss/ktrace on the offending program; I need to know if it's a flock, lockf, or fcntl based lock causing the problem for you. 2) Consider building a debug kernel. Since the option changes, I don't know if you can set "option LOCKF_DEBUG" in the kernel config or not, or under what conditions the debug sysctl's will show up. Best bet is to: a) build the kernel DEBUG to be sure to get the sysctl's b) At the top of /sys/kern/lockf.c, add "#define LOCKF_DEBUG"; if you are adventurous, you can try it as a kernel option; if it doesn't work, then the lockf_debug value won't show up in the sysctl output c) Get to the point where the bug *almost* is going to happen. d) sysctl lockf_debug to 1 (for entry logging), 2 (for overlap management), or 3 (for both). You will get a *lot* of debug output; if you have a small dmesg buffer, do them seperately 3) Send me the logs. I should be able to fix the problem very quickly. Thanks, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message