From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Gruenbacher Date: Wed, 10 Feb 2016 20:48:12 +0100 Subject: [Cluster-devel] DLM Shutdown In-Reply-To: <20160210173846.GA18813@redhat.com> References: <20160210173846.GA18813@redhat.com> Message-ID: List-Id: 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 6:38 PM, David Teigland wrote: > On Wed, Feb 10, 2016 at 02:33:49AM +0100, Andreas Gruenbacher wrote: >> never actively releases existing lockspaces. This means that as soon >> as any application creates the default lockspace (via libdlm), or if >> an application doesn't release any lockspaces it creates, dlm_controld >> will never shut down. > > You can simply run 'dlm_tool leave foo' (repeatedly if necessary) to remove > a lockspace. You could add a dlm_tool option that would trivially clear > all existing lockspaces this way. Hmm yes, that can be used to release unused lockspaces. I see that it even forces lockspaces to be released when there are still active locks. When a shutdown is requested, shouldn't dlm_controld really release lockspaces in a similar way as well? Thanks, Andreas