From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 3/3] ocfs2/dlm: Do not migrate resource to a node that is leaving the domain
Date: Thu, 05 May 2011 16:44:30 -0700 [thread overview]
Message-ID: <4DC3365E.20700@oracle.com> (raw)
In-Reply-To: <20110505232820.GG17822@wotan.suse.de>
On 05/05/2011 04:28 PM, Mark Fasheh wrote:
> On Thu, May 05, 2011 at 03:44:50PM -0700, Sunil Mushran wrote:
>> oops... that's a typo. It should be nodenum. Hey, you do remember
>> o2dlm. ;)
> Lol, glad to know I haven't totally lost it ;)
>
>
>> That check is superfluous. As in, that nodenum should always be in
>> the domain_map. But we've had that check from before and I'm trying
>> not to rock the boat too much.
> Maybe we should warn on it then?
The more I think about it, the more removal makes sense. But I may
need a shot of whiskey to fortify my resolve. ;)
next prev parent reply other threads:[~2011-05-05 23:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 23:03 [Ocfs2-devel] [PATCH 1/3] ocfs2/dlm: dlm_is_lockres_migrateable() returns boolean Sunil Mushran
2011-04-26 23:03 ` [Ocfs2-devel] [PATCH 2/3] ocfs2/dlm: Add new dlm message DLM_BEGIN_EXIT_DOMAIN_MSG Sunil Mushran
2011-05-05 22:12 ` Mark Fasheh
2011-04-26 23:03 ` [Ocfs2-devel] [PATCH 3/3] ocfs2/dlm: Do not migrate resource to a node that is leaving the domain Sunil Mushran
2011-05-05 22:24 ` Mark Fasheh
2011-05-05 22:44 ` Sunil Mushran
2011-05-05 23:28 ` Mark Fasheh
2011-05-05 23:44 ` Sunil Mushran [this message]
2011-05-10 6:19 ` Wengang Wang
2011-05-10 17:17 ` Sunil Mushran
2011-05-05 22:09 ` [Ocfs2-devel] [PATCH 1/3] ocfs2/dlm: dlm_is_lockres_migrateable() returns boolean Mark Fasheh
2011-05-05 22:15 ` Sunil Mushran
2011-05-24 6:53 ` Joel Becker
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=4DC3365E.20700@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.