Date: Mon, 29 Mar 2010 18:08:19 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: freebsd-stable@freebsd.org Subject: Re: Strange NFS-related messages (related to lockd/statd) Message-ID: <Pine.GSO.4.63.1003291800410.13379@muncher.cs.uoguelph.ca> In-Reply-To: <20100329165647.GA3796@icarus.home.lan> References: <20100329165647.GA3796@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 29 Mar 2010, Jeremy Chadwick wrote: > > I can't find a definition of what the acronyms NLM and NSM stand for, > nor does Googling the error messages return relevant results (except one > FreeBSD committer reporting similar, but nobody replied). I don't know > the implications of these messages. > NLM - Network Lock Manager NSM - Network Status Monitor (I think?) These two protocols (separate from NFS) were what Sun implemented in the 1980s to provide locking on NFS mount points. Imho, these protocols were poorly designed: - The NLM allows blocking locks at the server, which can cause assorted nasty issues when the client crashes or gets network partitioned. - It also depended on the NSM to decide when machines were up/down and the NSM protocol basically did this in a rather poor way. A big part of NFSv4 was the integration of locking, in order to avoid use of the above. (As you might have guessed, lockd and statd implement the above two protocols. rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1003291800410.13379>