https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-7190 Lustre <p>sanity-lfsck test 18a failed as follows:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>CMD: shadow-17vm12 /usr/sbin/lctl get_param -n mdd.lustre-MDT0000.lfsck_layout sanity-lfsck test_18a: @@@@@@ FAIL: (6.1) Expect 1 fixed on mds1, but got: 0 </pre> </div></div> <p>Maloo report: <a href="https://testing.hpdd.intel.com/test_sets/bf6d7fc0-5a65-11e5-9147-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/bf6d7fc0-5a65-11e5-9147-5254006e85c2</a></p> Lustre Build: <a href="https://build.hpdd.intel.com/job/lustre-master/3179">https://build.hpdd.intel.com/job/lustre-master/3179</a><br/> Distro/Arch: RHEL7.1/x86_64 LU-7190

sanity-lfsck test_18a: FAIL: (6.1) Expect 1 fixed on mds1, but got: 0

Bug Minor Resolved Fixed nasf Jian Yu Tue, 22 Sep 2015 00:38:53 +0000 Thu, 12 May 2016 18:57:47 +0000 Tue, 6 Oct 2015 14:24:38 +0000 Lustre 2.8.0 Lustre 2.8.0 0 6 <p>Hi Fan Yong,<br/> Could you have a look at this?<br/> Thanks.<br/> Joe</p> <p>The failure is caused by some unexpected MDT-OST connection issue. During the 2nd phase scanning, the layout LFSCK slave engine on the OST will query the master engine status from the MDT periodically. Sometimes, the query RPC may hit failure that may because network trouble, or the MDS node issues. To make the LFSCK can go ahead, the slave engine will not wait for ever, instead, it will assume the master engine has exited without notifying (or fail to notify) the slave engine. So the slave engine will exit also and clean up the LFSCK environment on the OST, including the OST-object access bitmap that is used to find out orphan OST-objects.</p> <p>On the other hand, the assumption of master engine exit maybe wrong. If the master engine does not exit, and the network trouble between the MDS and OSS recovered after the slave engine exited, then the master engine will try to find out orphan OST-objects during its 2nd phase scanning. But because the slave engine has already exited and released the OST-object access bitmap, the master engine has no way to find out orphan OST-objects. That is why test_18a failed.</p> <p>Fan Yong (fan.yong@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/16667" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16667</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7190" title="sanity-lfsck test_18a: FAIL: (6.1) Expect 1 fixed on mds1, but got: 0" class="issue-link" data-issue-key="LU-7190"><del>LU-7190</del></a> lfsck: tolerate MDT-OST communication failures<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: dac0ed16ab2493fd3ae4b53c8a30b356e9de5873</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/16667/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16667/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-7190" title="sanity-lfsck test_18a: FAIL: (6.1) Expect 1 fixed on mds1, but got: 0" class="issue-link" data-issue-key="LU-7190"><del>LU-7190</del></a> lfsck: tolerate MDT-OST communication failures<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 978458e05db4cad21e3ee32384168f53fd3e2d72</p> <p>Landed for 2.8</p> Related Development Rank 1|hzxoa7: Rank (Obsolete) 9223372036854775807 Severity