cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Patch: making DLM more robust
Date: Wed, 1 Dec 2010 12:27:56 -0500	[thread overview]
Message-ID: <20101201172756.GF26955@redhat.com> (raw)
In-Reply-To: <4CF6140D.7060809@bull.net>

On Wed, Dec 01, 2010 at 10:23:25AM +0100, Menyhart Zoltan wrote:
> If we cannot obtain a given resource within a limited time frame,
> then it is a real error for the customer: s/he cannot mount an OCFS2
> volume, cannot issue a cluster command, etc.

Matter of opinion and preference I suppose.

> >2. The difficulty, even with EINTR, is correctly and cleanly unwinding the
> >dlm_controld state.
> 
> Let's take this example indlm/libdlm/libdlm.c:

The problem is not backing out of libdlm, it's leaving the cpg group, etc
in dlm_controld (when the join itself is not even complete).  It should
all be possible, but I've never viewed this as a problem worth fixing
given the effort required.

Dave



      reply	other threads:[~2010-12-01 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 16:31 [Cluster-devel] "->ls_in_recovery" not released Menyhart Zoltan
2010-11-22 17:34 ` David Teigland
2010-11-23 14:58   ` Menyhart Zoltan
2010-11-23 17:15     ` David Teigland
2010-11-24 16:13       ` Menyhart Zoltan
2010-11-24 20:29         ` David Teigland
2010-11-30 16:57       ` [Cluster-devel] Patch: making DLM more robust Menyhart Zoltan
2010-11-30 17:30         ` David Teigland
2010-12-01  9:23           ` Menyhart Zoltan
2010-12-01 17:27             ` David Teigland [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=20101201172756.GF26955@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).