From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Teigland <teigland@redhat.com>
Date: Wed, 10 Feb 2016 14:18:24 -0600
Subject: [Cluster-devel] DLM Shutdown
In-Reply-To: <CAHc6FU7824i3-3MOjCAFX_SSk2aPqxX8tgP=ObSUfBkHw1pU8w@mail.gmail.com>
References: <CAHc6FU58TBA2hxVjeakQZ=vyzt6-nWdvTdewE2xtSLEyJU1yXA@mail.gmail.com>
	<20160210173846.GA18813@redhat.com>
	<CAHc6FU7824i3-3MOjCAFX_SSk2aPqxX8tgP=ObSUfBkHw1pU8w@mail.gmail.com>
Message-ID: <20160210201824.GA20841@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Wed, Feb 10, 2016 at 08:48:12PM +0100, Andreas Gruenbacher wrote:
> When a shutdown is requested, shouldn't dlm_controld really release
> lockspaces in a similar way as well?

You could probably do that if you check that the lockspace is managing no
local locks (which would be a pain).  If locks exist you'd not want to do
that without a force option at least.