Date: Sat, 12 Dec 2020 00:02:26 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: J David <j.david.lists@gmail.com> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Major issues with nfsv4 Message-ID: <YTOPR0101MB097041BD590A3D3EF2A65557DDCA0@YTOPR0101MB0970.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <CABXB=RSyN%2Bo2yXcpmYw8sCSUUDhN-w28Vu9v_cCWa-2=pLZmHg@mail.gmail.com> References: <CABXB=RRB2nUk0pPDisBQPdicUA3ooHpg8QvBwjG_nFU4cHvCYw@mail.gmail.com> <YQXPR0101MB096849ADF24051F7479E565CDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>, <CABXB=RSyN%2Bo2yXcpmYw8sCSUUDhN-w28Vu9v_cCWa-2=pLZmHg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
J David wrote:=0A= [lots of stuff snipped]=0A= >Even so, there may be no workaround for the simultaneous mount limit=0A= >as long as reserved ports are required. Solving the negative=0A= >interaction with nullfs seems like the only long-term fix.=0A= >=0A= >What would be a good next step there?=0A= Well, if you have a test system you can break, doing=0A= # nfsstat -c -E=0A= once it is constipated could be useful.=0A= =0A= Look for the numbers under=0A= OpenOwner Opens LockOwner ...=0A= and see if any of them are getting very large.=0A= =0A= rick=0A= =0A= Thanks!=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB097041BD590A3D3EF2A65557DDCA0>