From owner-freebsd-current@FreeBSD.ORG Fri Jun 28 14:49:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A9F6CB0D for ; Fri, 28 Jun 2013 14:49:35 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 942DE10DC for ; Fri, 28 Jun 2013 14:49:35 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,958,1363158000"; d="scan'208";a="69917250" Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx12-out.netapp.com with ESMTP; 28 Jun 2013 07:49:28 -0700 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Fri, 28 Jun 2013 07:49:28 -0700 From: "Eggert, Lars" To: freebsd-current Subject: Re: NFSv4 console messages (locks lost etc.) Thread-Topic: NFSv4 console messages (locks lost etc.) Thread-Index: AQHOdAnBkCLwXfwr6ECtjlyrKEz+QJlLp2KAgAADQ4A= Date: Fri, 28 Jun 2013 14:49:26 +0000 Message-ID: <767D9311-710A-4FE0-872F-6065C7F6821F@netapp.com> References: <5D7908FE-0E9B-4CBA-9DA1-28D3CA154994@netapp.com> In-Reply-To: <5D7908FE-0E9B-4CBA-9DA1-28D3CA154994@netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <2DC1D9CD929E794D84EC03D7E0811368@hq.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 14:49:35 -0000 Hi, On Jun 28, 2013, at 16:37, "Eggert, Lars" wrote: > On Jun 28, 2013, at 16:14, "Eggert, Lars" 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=