I have only done two NFS commits within that range.
1 - A trivial one that adds two new arguments always specified as 0,
     which has no change in semantics.
2 - One that only affects NFSv4 during dismount, so it shouldn't affect
     an NFSv3 mount.

Some things to try:
- get rid of rpc.statd and rpc.lockd and do the mount with the "nolockd"
- capture packets during the mount and look at them in wireshark, to
  see what is going on the wire.
- see if there are any patches applied to your net interface driver during
  that commit rev. range
- if you have any kind of firewall setup, get rid of that and see if that

Good luck with it, rick
From: Michael Butler <i...@protected-networks.net>
Sent: Friday, September 29, 2017 9:09:35 PM
To: freebsd-current
Cc: rmack...@freebsd.org
Subject: Can't NFS mount ZFS volume

Both client and server have been upgraded from SVN r324033 to r324089

Now I can't mount a ZFS dataset over NFS :-(

imb@toshi:/home/imb> sudo /sbin/mount -t nfs vm01:/usr/local/exports/ /mnt

imb@toshi:/home/imb> mount
/dev/ada0s3a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local, multilabel)
procfs on /proc (procfs, local)
linprocfs on /usr/compat/linux/proc (linprocfs, local)
linsysfs on /usr/compat/linux/sys (linsysfs, local)
vm01:/usr/local/exports on /mnt (nfs)

imb@toshi:/home/imb> sudo ls -l /mnt
ls: /mnt: Input/output error

The server shows the mount as being registered ..

imb@vm01:/home/imb> showmount -a
All mount points on localhost:

It takes some time to complete an umount request but it does complete,

Any thoughts?

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to