From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Peterson Date: Thu, 24 Mar 2016 08:34:08 -0400 (EDT) Subject: [Cluster-devel] [PATCH] GFS2: ignore unlock failures after withdraw In-Reply-To: <1458670187-26408-1-git-send-email-bmarzins@redhat.com> References: <1458670187-26408-1-git-send-email-bmarzins@redhat.com> Message-ID: <425387913.42613341.1458822848882.JavaMail.zimbra@redhat.com> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ----- Original Message ----- > After gfs2 has withdrawn the filesystem, it may still have many locks not > in the unlocked state. If it is using lock_dlm, it will failed trying > the unlocks since it has already unmounted the lock manager. Instead, it > should set the SDF_SKIP_DLM_UNLOCK flag on withdraw, to signal that > it can skip the lock_manager on unlocks, and failback to lock_nolock > style unlocking. > > Signed-off-by: Benjamin Marzinski Hi, Thanks. This is now applied to the for-next branch of the linux-gfs2 tree: https://git.kernel.org/cgit/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=3e11e530415027a57936545957126aff49267b76 Regards, Bob Peterson Red Hat File Systems