Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Jun 2006 00:19:09 +0200
From:      "Ronald Klop" <ronald-freebsd8@klop.yi.org>
To:        "Michael Collette" <Michael.Collette@testequity.com>, "Rong-en Fan" <grafan@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: NFS Locking Issue
Message-ID:  <op.tbxhl7x98527sy@localhost>
In-Reply-To: <44A4373A.4070507@TestEquity.com>
References:  <44A42009.7050103@TestEquity.com> <6eb82e0606291214s4faceaegb027c1951d0aa011@mail.gmail.com> <44A4373A.4070507@TestEquity.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Jun 2006 22:25:30 +0200, Michael Collette  
<Michael.Collette@TestEquity.com> wrote:

> Rong-en Fan wrote:
>> On 6/29/06, Michael Collette <Michael.Collette@testequity.com> wrote:
>>> 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.
>>  Try 6.1-STABLE, especially make sure you have
>>      $FreeBSD: src/usr.sbin/rpc.lockd/kern.c,v 1.16.2.1 2006/06/02
>> 01:20:58 rodrigc Exp $
>>  for usr.sbin/rpc.lockd/kern.c, and see if this helps.
>
> I am running STABLE on all my test boxes, and the problem is very much  
> there.  It's not everything that locks up though.  I'm able to bring X  
> up with twm, but unable to launch any Gnome or KDE applications without  
> them being stranded in a lock state.
>
> I sure would have loved for your suggestion to be correct.  For what  
> it's worth, all the boxes I'm working with are on STABLE no more than a  
> week old.  I ran fresh build worlds on all of them before getting the  
> rest of my configs going.
>
> Thanks,

Hello, I run my client with the -L mount option. This makes NFS locks  
local to the client, which is a workaround for me. If you depend on locks  
enforced on the server it wil not work.

Ronald.

-- 
  Ronald Klop
  Amsterdam, The Netherlands



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.tbxhl7x98527sy>