Linux client crashing FreeBSD NFS server (?)

L

last1

I have a very reliable FreeBSD server running NFSv3. It ran just fine for years until today when I wanted to have a Linux Suse machine as client.

The Linux client mounted just fine apparently but it somehow threw lockd all out of wack on the FreeBSD server to the point that other FreeBSD NFS clients started seeing their mounts go down. Anyone else heard of something similar happening ?

Here are the logs from the server: ( oex1 is the new Linux client )

Feb 27 16:01:02 zfs1 rpc.statd[3112]: Invalid hostname to sm_mon: oex1
Feb 27 16:01:02 zfs1 kernel: Local NSM refuses to monitor oex1
Feb 27 16:02:35 zfs1 kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416
Feb 27 16:03:00 zfs1 syslogd: last message repeated 1 times
Feb 27 16:05:05 zfs1 syslogd: last message repeated 5 times
Feb 27 16:15:06 zfs1 syslogd: last message repeated 24 times
Feb 27 16:16:21 zfs1 syslogd: last message repeated 3 times

And the FreeBSD clients would print:

Code: 
Feb 27 16:02:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:09:15 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:09:28 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:11:20 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:11:31 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:16:21 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfsnfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd not responding
Feb 27 16:16:22 basicwgo1 kernel: nfs server 192.168.1.235:/zfs/goem: lockd is alive again

What's going on ?
 
not really, this machine works just fine with all other clients...I'm surprised a client - even though it might be faulty, ill intended, who knows - can bring down the entire server. Something's not right here
 
last1 said:
not really, this machine works just fine with all other clients...I'm surprised a client - even though it might be faulty, ill intended, who knows - can bring down the entire server. Something's not right here
Click to expand...

FWIW Linux clients work fine for my NFS FreeBSD server with v3 and v4.
 
cracauer@ said:
FWIW Linux clients work fine for my NFS FreeBSD server with v3 and v4.
Click to expand...

ok, thanks. Do you know how I can see the used rsize/wsize values for FreeBSD clients nfs mounts ? mount -v doesn't show anything so it must be either auto-negotiated or some values that aren't printed (?).
Edit: found it myself, it's: nfsstat -m
 
last1 said:
ok, thanks. Do you know how I can see the used rsize/wsize values for FreeBSD clients nfs mounts ? mount -v doesn't show anything so it must be either auto-negotiated or some values that aren't printed (?).
Click to expand...

I don't know. I set them explicitly. Dunno where I got the values from.
 
You must log in or register to reply here.
Back
Top