Macklem from comment #23)
Hi Rick

The nfs server is nfs v3
It runs a raidz2 pool with sharenfs property on selected vdevs.
The OS is
15.0-ALPHA2 stable/15-n280129-deaa609d065d GENERIC amd64 1500064 1500064

It was source built on 14th Sept.

The nfs client is on a rpi2b+ running 16:current of 3rd Nov. Does the uarch
issue affect nfsv3 as well?

Here's nfsstat -m. Thank you for looking at this

# nfsstat -m
192.168.1.102:/data/src-rpi2b on /usr/src
nfsv3,tcp,resvport,nconnect=3D1,hard,cto,lockd,sec=3Dsys,acdirmin=3D3,acdir=
max=3D60,acregmin=3D5,acregmax=3D60,nametimeo=3D60,negnametimeo=3D60,rsize=
=3D65536,wsize=3D65536,readdirsize=3D65536,readahead=3D16,wcommitsize=3D419=
4304,timeout=3D120,retrans=3D2

192.168.1.102:/data/ccache-rpi2b on /var/cache/ccache
nfsv3,tcp,resvport,nconnect=3D1,hard,cto,lockd,sec=3Dsys,acdirmin=3D3,acdir=
max=3D60,acregmin=3D5,acregmax=3D60,nametimeo=3D60,negnametimeo=3D60,rsize=
=3D65536,wsize=3D65536,readdirsize=3D65536,readahead=3D16,wcommitsize=3D419=
4304,timeout=3D120,retrans=3D2

192.168.1.102:/data/ports-rpi2b on /usr/ports
nfsv3,tcp,resvport,nconnect=3D1,hard,cto,lockd,sec=3Dsys,acdirmin=3D3,acdir=
max=3D60,acregmin=3D5,acregmax=3D60,nametimeo=3D60,negnametimeo=3D60,rsize=
=3D65536,wsize=3D65536,readdirsize=3D65536,readahead=3D16,wcommitsize=3D419=
4304,timeout=3D120,retrans=3D2

192.168.1.102:/data/obj-rpi2b on /usr/obj
nfsv3,tcp,resvport,nconnect=3D1,hard,cto,lockd,sec=3Dsys,acdirmin=3D3,acdir=
max=3D60,acregmin=3D5,acregmax=3D60,nametimeo=3D60,negnametimeo=3D60,rsize=
=3D65536,wsize=3D65536,readdirsize=3D65536,readahead=3D16,wcommitsize=3D419=
4304,timeout=3D120,retrans=3D2

--=20
You are receiving this mail because:
You are the assignee for the bug.=