<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style>
<!--
@font-face
{font-family:SimSun}
@font-face
{font-family:SimSun}
@font-face
{font-family:Calibri}
@font-face
{font-family:SimSun}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:72.0pt 90.0pt 72.0pt 90.0pt}
div.WordSection1
{}
-->
</style>
</head>
<body lang="ZH-CN" link="blue" vlink="purple" style="">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hi All, </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">As we test with OCFS2, sometime the file system become read only. The log is bellows.</span></p>
<p class="MsoNormal"><span lang="EN-US">We had review the code and try to find the reason, but did not find any ways to avoid this issue.</span></p>
<p class="MsoNormal"><span lang="EN-US">All the nodes in the cluster reach the read only file system finally.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 12 15:38:30 node01 kernel: [173109.179478] OCFS2: ERROR (device dm-1): ocfs2_commit_truncate: Inode 8918280 has empty extent block at 8918280</span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 12 15:38:30 node01 kernel: [173109.179478]</span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 12 15:38:30 node01 kernel: [173109.179493] File system is now read-only due to the potential of on-disk corruption. Please run fsck.ocfs2 once the file system is unmounted.</span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 12 15:38:30 node01 kernel: [173109.232387] (libvirtd,7367,11):ocfs2_truncate_for_delete:574 ERROR: status = -30</span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 12 15:38:30 node01 kernel: [173109.232401] (libvirtd,7367,11):ocfs2_wipe_inode:743 ERROR: status = -30</span></p>
<p class="MsoNormal"><span lang="EN-US">Feb 12 15:38:30 node01 kernel: [173109.232408] (libvirtd,7367,11):ocfs2_delete_inode:1022 ERROR: status = -30</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">We had use the command of “fsck.ocfs –fpy” to repair the file system.</span></p>
<p class="MsoNormal"><span lang="EN-US">The repair procedures log is as below, there are some error about the inode data:
</span></p>
<p class="MsoNormal"><span lang="EN-US">fsck.ocfs2 1.6.3</span></p>
<p class="MsoNormal"><span lang="EN-US">Checking OCFS2 filesystem in /dev/dm-1:</span></p>
<p class="MsoNormal"><span lang="EN-US"> Label: o20140820105531</span></p>
<p class="MsoNormal"><span lang="EN-US"> UUID: F1AAAC6C765D480F9052946392C6527A</span></p>
<p class="MsoNormal"><span lang="EN-US"> Number of blocks: 2621440000</span></p>
<p class="MsoNormal"><span lang="EN-US"> Block size: 4096</span></p>
<p class="MsoNormal"><span lang="EN-US"> Number of clusters: 10240000</span></p>
<p class="MsoNormal"><span lang="EN-US"> Cluster size: 1048576</span></p>
<p class="MsoNormal"><span lang="EN-US"> Number of slots: 32</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">/dev/dm-1 was run with -f, check forced.</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 0a: Checking cluster allocation chains</span></p>
<p class="MsoNormal"><span lang="EN-US">[CHAIN_BITS] Chain 60 in allocator inode 519 has 36784 bits marked free out of 64512 total bits but the block groups in the chain have 36762 free out of 64512 total. Fix this by updating the chain record? y</span></p>
<p class="MsoNormal"><span lang="EN-US">[CHAIN_GROUP_BITS] Allocator inode 519 has 2071620 bits marked used out of 10240000 total bits but the chains have 2071642 used out of 10240000 total. Fix this by updating the inode counts? y</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 0b: Checking inode allocation chains</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 0c: Checking extent block allocation chains</span></p>
<p class="MsoNormal"><span lang="EN-US">^[Pass 1: Checking inodes and blocks.</span></p>
<p class="MsoNormal"><span lang="EN-US">[INODE_SPARSE_CLUSTERS] Inode 8918280 has 4294967286 clusters but its blocks fit in 0 clusters. Correct the number of clusters? y</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 2: Checking directory entries.</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 3: Checking directory connectivity.</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 4a: checking for orphaned inodes</span></p>
<p class="MsoNormal"><span lang="EN-US">[INODE_ORPHANED] Inode 8918280 was found in the orphan directory. Delete its contents and unlink it? y</span></p>
<p class="MsoNormal"><span lang="EN-US">Pass 4b: Checking inodes link counts.</span></p>
<p class="MsoNormal"><span lang="EN-US">[INODE_NOT_CONNECTED] Inode 8918281 isn't referenced by any directory entries. Move it to lost+found? y</span></p>
<p class="MsoNormal"><span lang="EN-US">[INODE_NOT_CONNECTED] Inode 8918282 isn't referenced by any directory entries. Move it to lost+found? y</span></p>
<p class="MsoNormal"><span lang="EN-US">All passes succeeded.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">We are using Linux kernel with version 3.13.
</span></p>
<p class="MsoNormal"><span lang="EN-US">Is there any way to fix it? Or any other patches?
</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks a lot.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
</div>
<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>