Date: Sat, 02 May 2009 17:21:50 -0400 From: Tom McLaughlin <tmclaugh@sdf.lonestar.org> To: Doug Rabson <dfr@rabson.org> Cc: current@freebsd.org Subject: Re: NFS lockd/statd lock up network connection Message-ID: <49FCB96E.1010604@sdf.lonestar.org> In-Reply-To: <A42E28AD-54AF-407D-9E5A-38A95A56DFBC@rabson.org> References: <49D851FC.4090103@sdf.lonestar.org> <A42E28AD-54AF-407D-9E5A-38A95A56DFBC@rabson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote, On 04/08/2009 03:20 PM: > On 5 Apr 2009, at 07:38, Tom McLaughlin wrote: > >> Hey, I have a recent -CURRENT box which has a mount exported from an >> OpenBSD NFS server. Recently I enabled lockd and statd on the machine >> but this has started to cause the network connection on the machine >> to lockup. I find the following in dmesg: >> >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> nfs server exports:/mnt/raid0/net/home: lockd not responding >> NLM: failed to contact remote rpcbind, stat = 5, port = 28416 >> >> Additionally I see this when trying to restart netif: >> >> em0: Could not setup receive structures >> >> I've tried building with NFS_LEGACYRPC but that has not changed >> anything. Additionally I've tested this on 7-STABLE and while lockd >> still does not work (so, looks like I'll still have to work around >> my need for NFS locking) the network connection at least does not >> lock up. Is what I'm seeing evidence of some further problem? > > It looks as if lockd is not running on the server. The NFS locking > protocol needs it enabled at both ends. Also, NFS_LEGACYRPC won't > affect this - the record locking code always uses the new RPC code. Hi Doug, lockd is runing on both ends. The problem appears to be with the system running out of mbuf clusters when using lockd. [1] For now I'm mounting the particular mount with nolockd as an option to get around this. I've gotten errors with my -STABLE box using this mount with lockd enabled but at least the system didn't run out of mbuf clusters and lose all network connectivity. tom [1] http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006433.html -- | tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org | | FreeBSD http://www.FreeBSD.org |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49FCB96E.1010604>