Ocfs2 devel - Mar 2016 - [patch 19/25] ocfs2: o2hb: add negotiate timer

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.

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.