From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] dlm: Don't delete misc device if lockspace removal fails
Date: Thu, 22 Mar 2007 11:24:57 +0000 [thread overview]
Message-ID: <1174562697.32601.174.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <4600F9A9.4050903@redhat.com>
Hi,
Now in the GFS2 -nmw git tree. Thanks,
Steve.
On Wed, 2007-03-21 at 09:23 +0000, Patrick Caulfield wrote:
> Currently if the lockspace removal fails the misc device associated with a
> lockspace is left deleted. After that there is no way to access the orphaned
> lockspace from userland.
>
> This patch recreates the misc device if th dlm_release_lockspace fails. I
> believe this is better than attempting to remove the lockspace first because
> that leaves an unattached device lying around. The potential gap in which there
> is no access to the lockspace between removing the misc device and recreating it
> is acceptable ... after all the application is trying to remove it, and only new
> users of the lockspace will be affected.
>
> Signed-Off-By: Patrick Caulfield <pcaulfie@redhat.com>
prev parent reply other threads:[~2007-03-22 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 9:23 [Cluster-devel] [PATCH] dlm: Don't delete misc device if lockspace removal fails Patrick Caulfield
2007-03-22 11:24 ` Steven Whitehouse [this message]
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=1174562697.32601.174.camel@quoit.chygwyn.com \
--to=swhiteho@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).