Date: Mon, 1 Jul 2013 08:36:24 +0000 From: "Eggert, Lars" <lars@netapp.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: NFSv4 console messages (locks lost etc.) Message-ID: <40542593-2411-421E-BE65-FB62E9D55703@netapp.com> In-Reply-To: <301292118.57276.1372466730396.JavaMail.root@uoguelph.ca> References: <301292118.57276.1372466730396.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Jun 29, 2013, at 2:45, Rick Macklem <rmacklem@uoguelph.ca> 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40542593-2411-421E-BE65-FB62E9D55703>