<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 6, 2014 at 1:58 PM, Kevin Swab <<a href="mailto:Kevin.Swab@colostate.edu" target="_blank">Kevin.Swab@colostate.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I had this same problem after upgrading a system to r151012. nlockmgr failed to start because "svc:/network/nfs/status:default" was disabled. I enabled that service, then nlockmgr was happy. </blockquote><div> </div><div>Just tried my 2nd system. r151010 nlockmgr starts after clearing maintenance mode. r151012 it will not start at all. nfs/status was enabled and online. </div><div>The commonality I see on the two systems I have tried is they are both part of an HA cluster. So they don't import the pool at boot, but RSF-1 imports it with cache mapped to a different location. </div><div>nlockmgr is becoming a real show stopper. </div><div>-Chip </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I've done 3 other upgrades to r151012 and none of them had a problem with nlockmgr... Kevin On 10/06/2014 09:56 AM, Schweiss, Chip wrote: > > > On Mon, Oct 6, 2014 at 9:59 AM, Dan McDonald <<a href="mailto:danmcd@omniti.com">danmcd@omniti.com</a> > <mailto:<a href="mailto:danmcd@omniti.com">danmcd@omniti.com</a>>> wrote: > > > On Oct 6, 2014, at 10:41 AM, Schweiss, Chip <<a href="mailto:chip@innovates.com">chip@innovates.com</a> > <mailto:<a href="mailto:chip@innovates.com">chip@innovates.com</a>>> wrote: > > > > > Anyone else seeing this in r151012? > > > > Any tips on collecting better information on this would be appreciated. > > I saw this in once in 012, but not as persistently as you have. It > cleared up for me with a single reboot, but that may have just been > because I got lucky w.r.t. statd. > > I take it "svcadm disable nlockmgr ; svcadm enable nlockmgr" doesn't > help? > > > I didn't think to try that. Tried rebooting, but that didn't help. I > was already past my maintenance window, so I resorted to backing out to > r151010. > > > > > And as for output, I've seen in /var/adm/messages what you have, per > the cited illumos bug (4518). > > > > I wasn't aware of any new NFS changes that may have caused this to > become exaggerated in r151012. But, it's not clear on what is > triggering this bug either. On my larger pool systems with lots of NFS > exports, almost every reboot causes this and a 'svcadm clear' fixes it. > > Is there something different that a disable and enable does? I can > likely get a small window in the next few days to give it a try. > > -Chip > > > _______________________________________________ > OmniOS-discuss mailing list > <a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a> > <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a> > -- ------------------------------------------------------------------- Kevin Swab UNIX Systems Administrator ACNS Colorado State University Phone: <a href="tel:%28970%29491-6572" value="+19704916572">(970)491-6572</a> Email: Kevin.Swab@ColoState.EDU GPG Fingerprint: 7026 3F66 A970 67BD 6F17 8EB8 8A7D 142F 2392 791C _______________________________________________ OmniOS-discuss mailing list <a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a> <a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a> </blockquote></div> </div></div>