From: Jeff Layton Subject: Re: [RFC] server's statd and lockd will not sync after its nfslock restart Date: Wed, 16 Dec 2009 08:49:02 -0500 Message-ID: <20091216084902.64f722ad@tlielax.poochiereds.net> References: <4B275EA3.9030603@cn.fujitsu.com> <4B28B5FD.5000103@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: Chuck Lever , "Trond.Myklebust" , "J. Bruce Fields" , NFSv3 list To: Mi Jinlong Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4954 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756695AbZLPNtU (ORCPT ); Wed, 16 Dec 2009 08:49:20 -0500 In-Reply-To: <4B28B5FD.5000103@cn.fujitsu.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Wed, 16 Dec 2009 18:27:09 +0800 Mi Jinlong wrote: > > The statd and lockd's state at server when nfslock restart: > > lockd statd | > | > host(monitored = 1) /sm/client | client get locks success at first > (locks) | > | > host(monitored = 1) /sm/client | nfslock stop (lockd release client's locks) > (no locks) | > | > host(monitored = 1) /sm/ | nfslock start (client reclaim locks) > (locks) | (but statd don't monitor it) > > note: host(monitored=1) means: client's host struct is created, and is marked be monitored. > (locks), (no locks)means: host strcut holds locks, or not. > /sm/client means: there have a file under /var/lib/nfs/statd/sm directory > /sm/ means: /var/lib/nfs/statd/sm is empty! > > Perhaps we ought to clear the cached list of monitored hosts (i.e. set them all to monitored = 0) when lockd gets a SIGKILL. -- Jeff Layton