From owner-freebsd-stable@FreeBSD.ORG Thu Jun 29 18:45:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4135016A412 for ; Thu, 29 Jun 2006 18:45:50 +0000 (UTC) (envelope-from Michael.Collette@TestEquity.com) Received: from smtp.testequity.com (gateway.testequity.com [205.147.14.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC9E44C53 for ; Thu, 29 Jun 2006 18:45:49 +0000 (GMT) (envelope-from Michael.Collette@TestEquity.com) Received: from smtp.priv.testequity.com (unknown [192.168.3.27]) by smtp.testequity.com (Postfix) with ESMTP id 840F313C41A; Thu, 29 Jun 2006 11:45:49 -0700 (PDT) Received: from [192.168.3.172] (mach172.priv.testequity.com [192.168.3.172]) by smtp.priv.testequity.com (Postfix) with ESMTP id 7848DC74B; Thu, 29 Jun 2006 11:45:49 -0700 (PDT) Message-ID: <44A42009.7050103@TestEquity.com> Date: Thu, 29 Jun 2006 11:46:33 -0700 From: Michael Collette Organization: TestEquity LLC User-Agent: Thunderbird 1.5.0.4 (X11/20060607) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: NFS Locking Issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2006 18:45:50 -0000 This last week I had been working on a test network to test out 6.1 prior to upgrading our production boxes from 5.4. That's when I ran across the rpc.lockd issues that have been discussed earlier. Our production setup has diskless clients running KDE, which due to this bug is now dead on 6.1. I also have my mail server delivering messages to a file server via NFS. I even have servers booting diskless with NFS provided file systems... all of which are dead on 6.1. The last discussion our bug updates I've seen on this issue were about 3 months ago. This leaves me with a number of questions I hope can be answered here on this list. Is NFS a big deal for most other users, or am I out here on the fringe using it as much as I do? Is anyone working on a fix for this? If so, is there any kind of time frame where this fix might be MFC'd to 6-STABLE? I guess I'm still just a bit stunned that a bug this obvious not only found it's way into the STABLE branch, but is still there. Maybe it's not as obvious as I think, or not many folks are using it? All I know for sure here is that if I had upgraded to 6.1 my network would have been crippled. Later on, -- Michael Collette IT Manager TestEquity LLC Michael.Collette@TestEquity.com