ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: jiangyiwen <jiangyiwen@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch 19/25] ocfs2: o2hb: add negotiate timer
Date: Mon, 28 Mar 2016 20:41:56 +0800	[thread overview]
Message-ID: <56F92694.20204@huawei.com> (raw)
In-Reply-To: <56F887AB.8050005@oracle.com>

On 2016/3/28 9:23, Junxiao Bi wrote:
> Hi Yiwen,
> 
> On 03/26/2016 10:54 AM, jiangyiwen wrote:
>> Hi, Junxiao
>> This patch may have a problem. That is journal of every nodes become
>> abort when storage down, and then when storage up, because journal
>> has become abort, all of operations of metadata will fail. So how to
>> restore environment? panic or reset? how to trigger?
> Journal aborted means io error was returned by storage, right?
> If so, o2hb_thread should also get io error, in this case, nego process
> will be bypassed, and nodes will be fenced at last, see "[patch 23/25]
> ocfs2: o2hb: don't negotiate if last hb fail".
> 
> Thanks,
> Junxiao.
>>
>> Thanks,
>> Yiwen Jiang.
> 
> 
> .
> 
yes, you are right, sorry I don't see this patch before.

But I understand the results of storage down should return IO error
rather than getting hang.

Thanks,
Yiwen Jiang.

  reply	other threads:[~2016-03-28 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 20:12 [Ocfs2-devel] [patch 19/25] ocfs2: o2hb: add negotiate timer akpm at linux-foundation.org
2016-03-24  2:50 ` Junxiao Bi
2016-03-26  2:54   ` jiangyiwen
2016-03-28  1:23     ` Junxiao Bi
2016-03-28 12:41       ` jiangyiwen [this message]
2016-03-28 16:42         ` Srinivas Eeda
2016-03-29  1:08           ` jiangyiwen

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=56F92694.20204@huawei.com \
    --to=jiangyiwen@huawei.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 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).