On Wed, 16 Dec 2009 18:27:09 +0800 Mi Jinlong <mijinlong@xxxxxxxxxxxxxx> 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 <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
