Return-Path: Date: Mon, 09 Jun 2008 13:59:03 -0400 To: Jeff Layton From: "Talpey, Thomas" Subject: Re: rapid clustered nfs server failover and hung clients -- how best to close the sockets? In-Reply-To: References: <20080609103137.2474aabd@tleilax.poochiereds.net> <484D6510.2010109@gmail.com> <20080609132425.5144557b@tleilax.poochiereds.net> Message-ID: Cc: linux-nfs@vger.kernel.org, lhh@redhat.com, nfsv4@linux-nfs.org, nhorman@redhat.com, Wendy Cheng List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org MIME-Version: 1.0 List-ID: At 01:51 PM 6/9/2008, Talpey, Thomas wrote: >and NSM/NLM. NSM provides only notification, there's no way for >either server to know for sure all the clients have completed >either switch-to or switch-back. Just in case it helps to understand why relying on NSM is so risky: Slides 16, 17 and 23, especially. Tom. _______________________________________________ NFSv4 mailing list NFSv4@linux-nfs.org http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4