All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2: o2hb: not fence self if storage down
Date: Mon, 23 May 2016 16:40:30 -0700	[thread overview]
Message-ID: <20160523234030.GP7633@wotan.suse.de> (raw)
In-Reply-To: <20160523145010.2e7f606d0db552d529d9253e@linux-foundation.org>

On Mon, May 23, 2016 at 02:50:10PM -0700, Andrew Morton wrote:
> On Wed,  2 Mar 2016 15:56:06 +0800 Junxiao Bi <junxiao.bi@oracle.com> wrote:
> 
> > 
> > Hi Mark,
> > 
> > This serial of patches is to fix the issue that when storage down,
> > all nodes will fence self due to write timeout.
> > With this patch set, all nodes will keep going until storage back
> > online, except if the following issue happens, then all nodes will
> > do as before to fence self.
> > 1. io error got
> > 2. network between nodes down
> > 3. nodes panic
> 
> Guys, can we please do a quick triple-check on this series?  I'd like
> to unload them this week.  Thanks.
> 
> I'll send out the current version in a few secs.

I'll go through them and give my review.

Thanks,
	--Mark


--
Mark Fasheh

  reply	other threads:[~2016-05-23 23:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  7:56 [Ocfs2-devel] ocfs2: o2hb: not fence self if storage down Junxiao Bi
2016-03-02  7:56 ` [Ocfs2-devel] [PATCH V2 1/6] ocfs2: o2hb: add negotiate timer Junxiao Bi
2016-03-02  7:56 ` [Ocfs2-devel] [PATCH V2 2/6] ocfs2: o2hb: add NEGO_TIMEOUT message Junxiao Bi
2016-03-02  7:56 ` [Ocfs2-devel] [PATCH V2 3/6] ocfs2: o2hb: add NEGOTIATE_APPROVE message Junxiao Bi
2016-03-02  7:56 ` [Ocfs2-devel] [PATCH V2 4/6] ocfs2: o2hb: add some user/debug log Junxiao Bi
2016-03-02  7:56 ` [Ocfs2-devel] [PATCH V2 5/6] ocfs2: o2hb: don't negotiate if last hb fail Junxiao Bi
2016-03-02  7:56 ` [Ocfs2-devel] [PATCH V2 6/6] ocfs2: o2hb: fix hb hung time Junxiao Bi
2016-05-23 21:50 ` [Ocfs2-devel] ocfs2: o2hb: not fence self if storage down Andrew Morton
2016-05-23 23:40   ` Mark Fasheh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-20  3:13 Junxiao Bi
2016-01-20  6:00 ` Gang He
2016-01-20  8:09   ` Junxiao Bi
2016-01-20  9:18 ` Joseph Qi
2016-01-20 13:27   ` Junxiao Bi
2016-01-21  0:46     ` Joseph Qi
2016-01-21  1:48       ` Junxiao Bi
2016-01-22  4:25         ` Joseph Qi
2016-01-22  5:08           ` Junxiao Bi
2016-01-21  8:34 ` rwxybh
2016-01-21  8:41   ` Junxiao Bi

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=20160523234030.GP7633@wotan.suse.de \
    --to=mfasheh@suse.de \
    --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.