Date: Thu, 19 Dec 2019 00:22:52 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Richard P Mackerras <mack63richard@gmail.com>, Daniel Braniss <danny@cs.huji.ac.il> Cc: "stable@freebsd.org" <stable@freebsd.org> Subject: Re: nfs lockd errors after NetApp software upgrade. Message-ID: <YQBPR0101MB1427F9BE658B9A46C7E08335DD520@YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <CAGfybS-3Rvs57=oGFEfii_9a=aWxPr6dEq1Y1LqHbLXK1ZKmXA@mail.gmail.com> References: <EBC4AD74-EC62-4C67-AB93-1AA91F662AAC@cs.huji.ac.il> <YQBPR0101MB1427411AFE335E869B9CF022DD530@YQBPR0101MB1427.CANPRD01.PROD.OUTLOOK.COM> <0121E289-D2AE-44BA-ADAC-4814CAEE676F@cs.huji.ac.il>, <CAGfybS-3Rvs57=oGFEfii_9a=aWxPr6dEq1Y1LqHbLXK1ZKmXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Richard P Mackerras wrote:=0A=
=0A=
>Hi,=0A=
>What software version is the NetApp using?=0A=
>Is the exported volume big?=0A=
>Is the vserver configured for 64bit identifiers?=0A=
>=0A=
>If you enable NFS V4.0 or 4.1 other NFS clients using defaults might mount=
NFSv4.x >unexpectedly after a reboot so you need to watch that.=0A=
The FreeBSD client always uses NFSv3 mounts by default. To get NFSv4 you mu=
st=0A=
explicitly specify the "nfsv4" or "vers=3D4" mount option. For NFSv4.1, you=
must=0A=
also specify "minorversion=3D1".=0A=
=0A=
The Linux distros I am familiar with will use the highest NFS version suppo=
rted by=0A=
the server by default. (I suspect some are using NFSv4.1 without realizing =
it,=0A=
which isn't necessarily bad.)=0A=
=0A=
nfsstat -m=0A=
will show you which version is actually in use for both FreeBSD and Linux.=
=0A=
=0A=
rick=0A=
=0A=
Cheers=0A=
=0A=
Richard=0A=
(NetApp admin)=0A=
=0A=
On Wed, 18 Dec 2019 at 15:46, Daniel Braniss <danny@cs.huji.ac.il<mailto:da=
nny@cs.huji.ac.il>> wrote:=0A=
=0A=
=0A=
> On 18 Dec 2019, at 16:55, Rick Macklem <rmacklem@uoguelph.ca<mailto:rmack=
lem@uoguelph.ca>> wrote:=0A=
>=0A=
> Daniel Braniss wrote:=0A=
>=0A=
>> Hi,=0A=
>> The server with the problems is running FreeBSD 11.1 stable, it was work=
ing fine for >several months,=0A=
>> but after a software upgrade of our NetAPP server it=92s reporting many =
lockd errors >and becomes catatonic,=0A=
>> ...=0A=
>> Dec 18 13:11:02 moo-09 kernel: nfs server fr-06:/web/www: lockd not resp=
onding=0A=
>> Dec 18 13:11:45 moo-09 last message repeated 7 times=0A=
>> Dec 18 13:12:55 moo-09 last message repeated 8 times=0A=
>> Dec 18 13:13:10 moo-09 kernel: nfs server fr-06:/web/www: lockd is alive=
again=0A=
>> Dec 18 13:13:10 moo-09 last message repeated 8 times=0A=
>> Dec 18 13:13:29 moo-09 kernel: sonewconn: pcb 0xfffff8004cc051d0: Listen=
queue >overflow: 194 already in queue awaiting acceptance (1 occurrences)=
=0A=
>> Dec 18 13:14:29 moo-09 kernel: sonewconn: pcb 0xfffff8004cc051d0: Listen=
queue >overflow: 193 already in queue awaiting acceptance (3957 occurrence=
s)=0A=
>> Dec 18 13:15:29 moo-09 kernel: sonewconn: pcb 0xfffff8004cc051d0: Listen=
queue >overflow: 193 already in queue awaiting acceptance =85=0A=
> Seems like their software upgrade didn't improve handling of NLM RPCs?=0A=
> Appears to be handling RPCs slowly and/or intermittently. Note that no on=
e=0A=
> tests it with IPv6, so at least make sure you are still using IPv4 for th=
e mounts and=0A=
> try and make sure IP broadcast works between client and Netapp. I think t=
he NLM=0A=
> and NSM (rpc.statd) still use IP broadcast sometimes.=0A=
>=0A=
we are ipv4 - we have our own class c :-)=0A=
> Maybe the network guys can suggest more w.r.t. why, but as I've stated be=
fore,=0A=
> the NLM is a fundamentally broken protocol which was never published by S=
un,=0A=
> so I suggest you avoid using it if at all possible.=0A=
well, at the moment the ball is on NetAPP court, and switching to NFSv4 at =
the moment is out of the question, it=92s=0A=
a production server used by several thousand students.=0A=
=0A=
>=0A=
> - If the locks don't need to be seen by other clients, you can just use t=
he "nolockd"=0A=
> mount option.=0A=
> or=0A=
> - If locks need to be seen by other clients, try NFSv4 mounts. Netapp fil=
ers=0A=
> should support NFSv4.1, which is a much better protocol that NFSv4.0.=
=0A=
>=0A=
> Good luck with it, rick=0A=
thanks=0A=
danny=0A=
=0A=
> =85=0A=
> any ideas?=0A=
>=0A=
> thanks,=0A=
> danny=0A=
>=0A=
> _______________________________________________=0A=
> freebsd-stable@freebsd.org<mailto:freebsd-stable@freebsd.org> mailing lis=
t=0A=
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable=0A=
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org<=
mailto:freebsd-stable-unsubscribe@freebsd.org>"=0A=
=0A=
_______________________________________________=0A=
freebsd-stable@freebsd.org<mailto:freebsd-stable@freebsd.org> mailing list=
=0A=
https://lists.freebsd.org/mailman/listinfo/freebsd-stable=0A=
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org<ma=
ilto:freebsd-stable-unsubscribe@freebsd.org>"=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQBPR0101MB1427F9BE658B9A46C7E08335DD520>