> On 19 Dec 2019, at 02:22, Rick Macklem wrote:
>
> Richard P Mackerras wrote:
>
>> Hi,
>> What software version is the NetApp using?
>> Is the exported volume big?
>> Is the vserver configured for 64bit identifiers?
>>
>> If you enable NFS V4.0 or 4.1 other NFS clients using defaults might m
Daniel Braniss wrote:
[stuff snipped]
>all mounts are nfsv3/tcp
This doesn't affect what the NLM code (rpc.lockd) uses. I honestly don't know
when
the NLM uses tcp vs udp. I think rpc.statd still uses IP broadcast at times.
To me, it looks like a network configuration issue.
You could capture pac
> On 19 Dec 2019, at 16:09, Rick Macklem wrote:
>
> Daniel Braniss wrote:
> [stuff snipped]
>> all mounts are nfsv3/tcp
> This doesn't affect what the NLM code (rpc.lockd) uses. I honestly don't know
> when
> the NLM uses tcp vs udp. I think rpc.statd still uses IP broadcast at times.
can the
Hi,
At ONTAP 9.3P6 there is a possible LACP group issue after upgrade. Have you
checked any LACP groups,
These should not be a problem but I assume network interfaces are at the
home ports, not on slower ports or something silly. It is marginally better
if the traffic goes direct to the node where
Try changing bool_t do_tcp = FALSE; to TRUE in
/usr/src/sys/nlm/nlm_prot_impl.c, recompile the kernel and try again. I
think this makes it match Linux client behavior. I suspect I ran into
the same issue as you. I do think I used nolockd is a workaround
temporarily. I can provide some more details
