Date: Fri, 28 Jun 2013 14:49:26 +0000 From: "Eggert, Lars" <lars@netapp.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: NFSv4 console messages (locks lost etc.) Message-ID: <767D9311-710A-4FE0-872F-6065C7F6821F@netapp.com> In-Reply-To: <5D7908FE-0E9B-4CBA-9DA1-28D3CA154994@netapp.com> References: <B6B995D8-3D5D-4669-9588-790772816092@netapp.com> <5D7908FE-0E9B-4CBA-9DA1-28D3CA154994@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Jun 28, 2013, at 16:37, "Eggert, Lars" <lars@netapp.com> wrote: > On Jun 28, 2013, at 16:14, "Eggert, Lars" <lars@netapp.com> wrote: >> on a -CURRENT client, I get quite a number of console messages under hea= vy NFSv4 load, such as: >>=20 >> nfsv4 expired locks lost >> nfscl: never fnd open >=20 > actually, not sure if the "nfscl" message is from an NFSv4 mount point or= not, because the box mounts root via BOOTP, so with NFSv3 (or v2?) and som= e other mounts with NFSv4. and another data point: the "nfscl" messages seem to disappear when I remov= e the BOOTP_NFSV3 flag from the kernel. The client hangs that made me dig i= nto these messages seem to also disappear, fingers crossed. (I still get a bunch of "nfsv4 expired locks lost" messages, but no hangs.) Lars=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?767D9311-710A-4FE0-872F-6065C7F6821F>