From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] DLM Shutdown
Date: Wed, 10 Feb 2016 15:16:30 -0600 [thread overview]
Message-ID: <20160210211630.GA21379@redhat.com> (raw)
In-Reply-To: <CAHc6FU4WgA6gKDLpPCw+9arz3rQb_7C0=OFOZ6LY25OVg5jgaA@mail.gmail.com>
On Wed, Feb 10, 2016 at 09:38:58PM +0100, Andreas Gruenbacher wrote:
> On Wed, Feb 10, 2016 at 9:18 PM, David Teigland <teigland@redhat.com> wrote:
> > 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.
>
> Is that not what dlm_release_lockspace() with force set to false is
> supposed to do? It's weird that the operation may have to be repeated
> several times before the lockspace finally goes away; that could be
> improved with an additional flag to DLM_USER_REMOVE_LOCKSPACE.
OK, yes, but we've wandered into the weeds here. dlm_controld isn't
involved in lockspace lifetimes, that's the application/libdlm side.
The question is what behavior the program creating/removing the lockspace
needs (and if the program is for more than just testing.)
next prev parent reply other threads:[~2016-02-10 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 1:33 [Cluster-devel] DLM Shutdown Andreas Gruenbacher
2016-02-10 17:38 ` David Teigland
2016-02-10 19:48 ` Andreas Gruenbacher
2016-02-10 20:18 ` David Teigland
2016-02-10 20:38 ` Andreas Gruenbacher
2016-02-10 21:16 ` David Teigland [this message]
2016-02-10 22:08 ` Andreas Gruenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160210211630.GA21379@redhat.com \
--to=teigland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).