From owner-freebsd-current@FreeBSD.ORG Mon Jul 1 08:36:32 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 C26AFB44 for ; Mon, 1 Jul 2013 08:36:32 +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 AD961185D for ; Mon, 1 Jul 2013 08:36:32 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.87,972,1363158000"; d="scan'208";a="70515621" Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx12-out.netapp.com with ESMTP; 01 Jul 2013 01:36:25 -0700 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.35]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Mon, 1 Jul 2013 01:36:25 -0700 From: "Eggert, Lars" To: Rick Macklem Subject: Re: NFSv4 console messages (locks lost etc.) Thread-Topic: NFSv4 console messages (locks lost etc.) Thread-Index: AQHOdAnBkCLwXfwr6ECtjlyrKEz+QJlLp2KAgAADQ4CAAKaIAIADqD4A Date: Mon, 1 Jul 2013 08:36:24 +0000 Message-ID: <40542593-2411-421E-BE65-FB62E9D55703@netapp.com> References: <301292118.57276.1372466730396.JavaMail.root@uoguelph.ca> In-Reply-To: <301292118.57276.1372466730396.JavaMail.root@uoguelph.ca> 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: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: freebsd-current 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: Mon, 01 Jul 2013 08:36:32 -0000 Hi, On Jun 29, 2013, at 2:45, Rick Macklem wrote: > Btw, a NFSv4 mounted root fs will not work correctly, because the client > name is generated from the host uuid, which isn't set when the root fs > is mounted. I'm not sure what the client would use as its client name, > but this will definitely break things badly if multiple clients use the > same name. (And this might explain the lease expiry problem.) ah, now that explains a lot. Since these are diskless clients, I had set ho= stid_enable=3D"NO" in order to turn off the "/etc/rc: WARNING: could not st= ore hostuuid in /etc/hostid" warning. Turning this back on seems to have fixed the issue. (It might make sense to have the NFSv4 code throw a warning when the hostid= isn't set, if it depends on it?) Thanks, Lars=