From owner-freebsd-net@FreeBSD.ORG Thu Jan 11 16:17:56 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65C7216A403 for ; Thu, 11 Jan 2007 16:17:56 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2AD0113C46B for ; Thu, 11 Jan 2007 16:17:56 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id 8810E3F17; Thu, 11 Jan 2007 17:17:54 +0100 (CET) Date: Thu, 11 Jan 2007 17:17:54 +0100 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070111161754.GA955@zen.inc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: All mail clients suck. This one just sucks less. Subject: NFS locking broken X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 16:17:56 -0000 Hi all. Summary of the problem: since a few days, one of my FreeBSD workstations can't lock anymore files on a NFS filesystem. More details: I have a NFS server (on a old Linux box, but that's not the problem, it works) and some workstations. Everything worked fine until a few days ago. It may not be related, but problems started just after I made a big portupgrade of the problematic workstation (last portupgrade was made 1 or 2 months ago). Now, when I boot this workstation (which mounts one NFS partition on boot), I may have time (less than 5 minuts) to do a few NFS locks on the partition (/home), then NFS locking stops working, and all lock requests will be blocked (top says programs are on state "lockd", and rpc.lockd is seen twice, on in "select" state and the other in "nfslock" state). If I stop/start /etc/rc.d/nfslocking, it may restart for a few minuts (but not always), then will block again. Everything else is still ok, including network, DNS, other NFS operations (non locked read/writes), etc... If, at the same time, I try to do some NFS locks from other clients (Ubuntu, other FreeBSD6 but not up to date stations, etc...) to the same host/same partition, it will work (some of the hosts are on the same switch as the problematic workstation). After some time, I'll have messages on NFS server's console telling that rpc on timed out. I'll have no debug/warning/message on the FreeBSD workstation. I just tried to upgrade my base system to latest 6.2-PRERELEASE (was in 6.1 before), and I still have the problem. Did someone noticed similar problem ? Could this problem really be related to my portupgrade ? The only started service from /usr/local/etc/rc.d is cups, which doesn't use the NFS partition. My /etc/rc.conf DOES include: nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" rpcbind_enable="YES" And, most important for me: how can I fix that, or, at least, how can I generate some debug/informations on the box ? Thanks, Yvan.