NFS lockd problem

Giulio Ferro

unread,

Mar 26, 2010, 6:08:26 AM3/26/10

to

Outset:
1 NFS server (with lockd)
2 NFS client (with lockd)

The clients serve several jails with apache, whose data (www) resides on
the server

From time to time everything seem to freeze. Then, after one minute or
so, the system
works again as nothing had happened.

In these occasions I get this in the logs on the client madchines:
Mar 26 10:29:38 virt1 kernel: nfs server
192.168.40.121:/data/mount_servers/wwwsec/www: lockd not responding

followed shortly after by:

Mar 26 10:29:38 virt1 kernel: nfs server
192.168.40.121:/data/mount_servers/wwwsec/www: lockd is alive again

On the server I only get this:
Mar 26 10:29:31 data1 kernel: NLM: failed to contact remote rpcbind,
stat = 5, port = 28416

I don't think it's a network problem, since all connections are local
and high speed (1Gb/s)

I must admit that, with the other nfs problem I reported weeks ago, this
kind of freebsd system seems
less than stable to me, and this is very disappointing...

Anyway I'd appreciate any pointer on this issue...
_______________________________________________
freeb...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net...@freebsd.org"

Chuck Swiger

unread,

Mar 27, 2010, 2:50:17 PM3/27/10

to

On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote:
> Outset:
> 1 NFS server (with lockd)
> 2 NFS client (with lockd)
>
> The clients serve several jails with apache, whose data (www) resides on the server

If you need file locking to work reliably, you pretty much have to give up on using NFS + rpc.lockd and run against a local UFS filesystem.

Regards,
--
-Chuck

Ronald Klop

unread,

Mar 28, 2010, 6:19:59 AM3/28/10

to

On Sat, 27 Mar 2010 20:50:17 +0200, Chuck Swiger <csw...@mac.com> wrote:

> On Mar 26, 2010, at 3:08 AM, Giulio Ferro wrote:
>> Outset:
>> 1 NFS server (with lockd)
>> 2 NFS client (with lockd)
>>
>> The clients serve several jails with apache, whose data (www) resides
>> on the server
>
> If you need file locking to work reliably, you pretty much have to give
> up on using NFS + rpc.lockd and run against a local UFS filesystem.

I don't have this experience. I use NFS locking between FreeBSD, Linux,
NetApp and SUN stuff. Older versions of FreeBSD had some troubles, but
more recent ones work very well.

Ronald.

Ronald Klop

unread,

Mar 28, 2010, 6:24:23 AM3/28/10

to

On Fri, 26 Mar 2010 12:08:26 +0200, Giulio Ferro <au...@zirakzigil.org>
wrote:

> Outset:
> 1 NFS server (with lockd)
> 2 NFS client (with lockd)
>
> The clients serve several jails with apache, whose data (www) resides on
> the server
>

> From time to time everything seem to freeze. Then, after one minute or
> so, the system
> works again as nothing had happened.
>
> In these occasions I get this in the logs on the client madchines:
> Mar 26 10:29:38 virt1 kernel: nfs server
> 192.168.40.121:/data/mount_servers/wwwsec/www: lockd not responding
>
> followed shortly after by:
>
> Mar 26 10:29:38 virt1 kernel: nfs server
> 192.168.40.121:/data/mount_servers/wwwsec/www: lockd is alive again
>
>
> On the server I only get this:
> Mar 26 10:29:31 data1 kernel: NLM: failed to contact remote rpcbind,
> stat = 5, port = 28416
>
> I don't think it's a network problem, since all connections are local
> and high speed (1Gb/s)
>
> I must admit that, with the other nfs problem I reported weeks ago, this
> kind of freebsd system seems
> less than stable to me, and this is very disappointing...
>
> Anyway I'd appreciate any pointer on this issue...

I'm no NFS expert, so I don't know if I can help, but regularly people
want to know your FreeBSD version(s), your used NFS version, if you are
running NFS over TCP or UDP. Does it help to switch between UDP/TCP?