Return-Path: Received: from tac.ki.iif.hu ([193.6.222.43]:52673 "EHLO tac.ki.iif.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750820Ab1BKMSb (ORCPT ); Fri, 11 Feb 2011 07:18:31 -0500 Received: from wferi by tac.ki.iif.hu with local (Exim 4.72) (envelope-from ) id 1PnrxF-0006xD-Cx for linux-nfs@vger.kernel.org; Fri, 11 Feb 2011 13:18:29 +0100 From: Ferenc Wagner To: linux-nfs@vger.kernel.org Subject: server does not abort grace period Date: Fri, 11 Feb 2011 13:18:29 +0100 Message-ID: <87wrl6ix2i.fsf@tac.ki.iif.hu> Content-Type: text/plain; charset=us-ascii Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 Hi, We're running 2.6.32 (Debian squeeze) NFS4 server and clients. The server boots and runs purely from SAN, so we can start it on different computers. In case of such "hardware failovers" I'd expect the clients to quickly reclaim their locks (if any) and thus the server to abort it's 90-second grace period early. However, this does not happen, ruining our HA like, totally. So, the questions: is the functionality of aborting the grace period early missing from version 2.6.32 of the Linux kernel? If yes, is it present in any kernel version? If it should work, could someone offer some advice on debugging it? If it isn't supported, what's the best practice of providing highly available NFSv4 today? -- Thanks, Feri.