<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>
<!--
body
        {line-height:1.5}
blockquote
        {margin-top:0px;
        margin-bottom:0px;
        margin-left:0.5em}
p
        {margin-top:0px;
        margin-bottom:0px}
body
        {font-size:16pt;
        font-family:微软雅黑;
        color:rgb(0,0,0);
        line-height:1.5}
-->
</style>
</head>
<body>
<div><span style="font-size:small; line-height:19px">Hi,</span></div>
<div><font size="2"><span></span><span style="line-height:19px">"status = -30" means it has encountered EROFS when start transaction.</span><br style="line-height:19px">
<span style="line-height:19px">And system panic is because </span><span style="line-height:19px">s_mount_opt</span><span style="line-height:19px"> </span><span style="line-height:19px">is set to </span><span style="line-height:19px">OCFS2_MOUNT_ERRORS_PANIC </span><span style="line-height:19px">in </span><span style="line-height:19px"> </span><span style="line-height:1.5">__ocfs2_abort, </span></font></div>
<div style="widows:1"><font size="2"><span style="line-height:30px">i</span><span style="widows:1; line-height:1.5">deal with
</span><span style="line-height:19px">OCFS2_MOUNT_ERRORS_PANIC </span><span style="line-height:1.5; widows:1">first </span></font><span style="background-color:window; font-size:small; line-height:30px">in </span><span style="background-color:window; font-size:small; line-height:19px">ocfs2_handle_error.</span></div>
<div style="widows:1"><span style="background-color:window; font-family:微软雅黑,Tahoma; font-size:small; line-height:normal">so I think that it is not reasona</span><font size="2" style="background-color:window"><span style="line-height:normal">ble, </span><span style="line-height:30px">Therefore,
this setting shall be canceled in </span></font><span style="font-size:small; line-height:19px; background-color:window">__ocfs2_abort.</span></div>
<div style="widows:1"><span style="font-size:small; line-height:19px; background-color:window"> thanks </span></div>
<div><br>
</div>
<hr color="#b5c4df" size="1" align="left" style="width:210px; height:1px">
<div><span>
<div style="margin:10px; font-family:verdana; font-size:10pt">
<div>zhangguanghui</div>
</div>
</span></div>
<blockquote style="margin-top:0px; margin-bottom:0px; margin-left:0.5em">
<div> </div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<div style="padding-right:8px; padding-left:8px; font-size:12px; font-family:tahoma; color:#000000; background:#efefef; padding-bottom:8px; padding-top:8px">
<div><b>From:</b> <a href="mailto:joseph.qi@huawei.com">Joseph Qi</a></div>
<div><b>Date:</b> 2015-10-14 16:13</div>
<div><b>To:</b> <a href="mailto:zhang.guanghui@h3c.com">zhangguanghui 10102 (CCPL)</a></div>
<div><b>CC:</b> <a href="mailto:mfasheh@suse.de">mfasheh ></a>; <a href="mailto:ocfs2-users@oss.oracle.com">
'ocfs2-users@oss.oracle.com' (ocfs2-users@oss.oracle.com)</a>; <a href="mailto:ocfs2-devel@oss.oracle.com">
ocfs2-devel@oss.oracle.com</a>; <a href="mailto:rgoldwyn@suse.com">rgoldwyn</a></div>
<div><b>Subject:</b> Re: [Ocfs2-devel] Ocfs2-devel Digest, Vol 138, Issue 31 review</div>
</div>
</div>
<div>
<div class="FoxDiv20151014162010612382">
<p><font size="2">On 2015/10/14 15:49, Zhangguanghui wrote:<br>
> OCFS2 is often used in high-availaibility systems, This patch enhances robustness for the filesystem.<br>
> but storage network is unstable,it still triggers a panic, such as ocfs2_start_trans -> __ocfs2_abort ->panic.<br>
> The 's_mount_opt' should depend on the mount option set, If errors=continue is set,<br>
> mark as a EIO error, change OCFS2_MOUNT_ERRORS_PANIC to OCFS2_MOUNT_ERRORS_CONT in __ocfs2_abort;<br>
> it's better than forcing a panic without decreasing availability,errors=continue seems be well to me.<br>
><br>
> Finally, any feedback about this process (positive or negative) would be greatly appreciated.<br>
><br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.787906] (pool,23256,12):ocfs2_start_trans:367 ERROR: status = -30<br>
><br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825046] CPU: 12 PID: 23256 Comm: pool Tainted: GF W IO 3.13.6 #1<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825050] Hardware name: HP ProLiant BL460c G7, BIOS I27 12/03/2012<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825054] ffffffffffffffe2 ffff88108c945a88 ffffffff81750690 ffff88180bacfff0<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825064] ffff88174196d000 ffff88108c945ad8 ffffffffa052f667 ffffffffffffffe2<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825072] 0000000000001000 ffff88108c945b58 ffff88175e870000 ffff8811ada4f000<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825087] Call Trace:<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825103] [<ffffffff81750690>] dump_stack+0x46/0x58<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825154] [<ffffffffa052f667>] ocfs2_start_trans+0x1d7/0x200 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825183] [<ffffffffa0505b60>] ocfs2_write_begin_nolock+0xda0/0x1c70 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825216] [<ffffffffa052b7cb>] ? ocfs2_read_inode_block_full+0x3b/0x60 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825248] [<ffffffffa051a82f>] ? ocfs2_inode_lock_full_nested+0x52f/0xc60 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825277] [<ffffffffa0516060>] ? ocfs2_should_refresh_lock_res+0x80/0x190 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825304] [<ffffffffa0506b36>] ocfs2_write_begin+0x106/0x230 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825330] [<ffffffffa05180ab>] ? __ocfs2_cluster_unlock.isra.27+0x9b/0xe0 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825342] [<ffffffff8115342b>] generic_file_buffered_write+0xfb/0x280<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825370] [<ffffffffa051a1c5>] ? ocfs2_rw_lock+0x75/0x1b0 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825398] [<ffffffffa0527f3f>] ocfs2_file_aio_write+0x79f/0x830 [ocfs2]<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825407] [<ffffffff811c14ba>] do_sync_write+0x5a/0x90<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825413] [<ffffffff811c1fc5>] vfs_write+0xc5/0x1f0<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825418] [<ffffffff811c24c2>] SyS_write+0x52/0xa0<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825426] [<ffffffff8176106d>] system_call_fastpath+0x1a/0x1f<br>
> Aug 11 11:32:25 cvknode73 kernel: [678904.825431] OCFS2: abort (device sdu): ocfs2_start_trans: Detected aborted journal<br>
><br>
"status = -30" means it has encountered EROFS when start transaction.<br>
And system panic is because you mount with option "errors=panic",<br>
while default is "errors=remount-ro" rather than panic.<br>
Change it to "errors=continue" will proceed even if filesystem<br>
encounters errors (default will set it to readonly).<br>
<br>
Thanks,<br>
Joseph<br>
<br>
><br>
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!<br>
---<br>
> zhangguanghui<br>
<br>
<br>
</font></p>
</div>
</div>
</blockquote>
<span style="font-size:7.5pt; font-family:华文细黑; color:gray"><span lang="EN-US">-------------------------------------------------------------------------------------------------------------------------------------<br>
</span>本邮件及其附件含有杭州华三通信技术有限公司的保密信息,仅限于发送给上面地址中列出<span lang="EN-US"><br>
</span>的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、<span lang="EN-US"><br>
</span>或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本<span lang="EN-US"><br>
</span>邮件!<span lang="EN-US"><br>
</span></span><span lang="EN-US" style="font-size:7.5pt; font-family:"Arial","sans-serif"; color:gray">This e-mail and its attachments contain confidential information from H3C, which is
<br>
intended only for the person or entity whose address is listed above. Any use of the
<br>
information contained herein in any way (including, but not limited to, total or partial
<br>
disclosure, reproduction, or dissemination) by persons other than the intended <br>
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
<br>
by phone or email immediately and delete it!</span>
</body>
</html>